Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7ae55aaf36ee94306cc7d1cc26ba69e6cca73ccbcee7af875bf19bc80a1477ff

Tx prefix hash: 75f529ad252071e6adf99d80a8b2d53689edb06ed6ea8d225a512c035b6f2357
Tx public key: d38f73272903c29ec796aa8f0a14424eeef8f42a91e2d190a28a6b2eb051f346
Timestamp: 1720859536 Timestamp [UCT]: 2024-07-13 08:32:16 Age [y:d:h:m:s]: 00:134:09:24:18
Block: 1064696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96151 RingCT/type: yes/0
Extra: 01d38f73272903c29ec796aa8f0a14424eeef8f42a91e2d190a28a6b2eb051f34602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80d6476c524266e995c3206113904e53e6a3320e9885d969fdb886bf84ce614e 0.600000000000 1535229 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1064706, "vin": [ { "gen": { "height": 1064696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80d6476c524266e995c3206113904e53e6a3320e9885d969fdb886bf84ce614e" } } ], "extra": [ 1, 211, 143, 115, 39, 41, 3, 194, 158, 199, 150, 170, 143, 10, 20, 66, 78, 238, 248, 244, 42, 145, 226, 209, 144, 162, 138, 107, 46, 176, 81, 243, 70, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8