Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9465c64010ecfea589f9a48f1017e16f9293c9338667283c00bba8b38ff678f

Tx prefix hash: ec46bcac590a1c9df3c283f4b157cf36c89c979d54787163a2f8ae7d55aeae4d
Tx public key: 730dc36e3051a624042fe93d21d6a7f1d05a22fcac2ce9e4515d700a0b40352d
Timestamp: 1717670335 Timestamp [UCT]: 2024-06-06 10:38:55 Age [y:d:h:m:s]: 01:155:03:54:35
Block: 1038250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369458 RingCT/type: yes/0
Extra: 01730dc36e3051a624042fe93d21d6a7f1d05a22fcac2ce9e4515d700a0b40352d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19752d662f65be13b18af6f99b762f3b8033d9219f62b2fc749970216df2c46f 0.600000000000 1506811 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": 1038260, "vin": [ { "gen": { "height": 1038250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19752d662f65be13b18af6f99b762f3b8033d9219f62b2fc749970216df2c46f" } } ], "extra": [ 1, 115, 13, 195, 110, 48, 81, 166, 36, 4, 47, 233, 61, 33, 214, 167, 241, 208, 90, 34, 252, 172, 44, 233, 228, 81, 93, 112, 10, 11, 64, 53, 45, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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