Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7442270cafd3b9ca9a795709cb7830b8f32f2849253c3a52336412cb571f45a

Tx prefix hash: c7197dac996a71ae8c94bfd5fa711e4babbf3c237c8d2062e7c333235027690e
Tx public key: 3c6046eeb91a1f1ac9556e7980665a99673fa4d97cd6c7298e20f978dfb5ace5
Timestamp: 1730407162 Timestamp [UCT]: 2024-10-31 20:39:22 Age [y:d:h:m:s]: 00:023:14:54:29
Block: 1143757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16899 RingCT/type: yes/0
Extra: 013c6046eeb91a1f1ac9556e7980665a99673fa4d97cd6c7298e20f978dfb5ace50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 505e34a134762d9f26273ade2e05ed3d5d26492a61140166ac61ec617a25fd3e 0.600000000000 1627740 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": 1143767, "vin": [ { "gen": { "height": 1143757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "505e34a134762d9f26273ade2e05ed3d5d26492a61140166ac61ec617a25fd3e" } } ], "extra": [ 1, 60, 96, 70, 238, 185, 26, 31, 26, 201, 85, 110, 121, 128, 102, 90, 153, 103, 63, 164, 217, 124, 214, 199, 41, 142, 32, 249, 120, 223, 181, 172, 229, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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