Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78c366c5c115d6f8f1c3540de9b5d9af767f1222340ea441945345aef0b29a14

Tx prefix hash: 120efc2a7747bb27de11c3555b98a3dd6dbfb1424b9a6e6cf3a1531bf8002c25
Tx public key: b6f3527e8e3e4de59ce474640517d9caa23670e100814cf3abfb61b16693df1d
Timestamp: 1714877490 Timestamp [UCT]: 2024-05-05 02:51:30 Age [y:d:h:m:s]: 00:340:00:39:33
Block: 1015096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243054 RingCT/type: yes/0
Extra: 01b6f3527e8e3e4de59ce474640517d9caa23670e100814cf3abfb61b16693df1d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 659d730ca7436453539678a1b750e79e312df1a3ed58454506bde3d60f1396fd 0.600000000000 1478367 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": 1015106, "vin": [ { "gen": { "height": 1015096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "659d730ca7436453539678a1b750e79e312df1a3ed58454506bde3d60f1396fd" } } ], "extra": [ 1, 182, 243, 82, 126, 142, 62, 77, 229, 156, 228, 116, 100, 5, 23, 217, 202, 162, 54, 112, 225, 0, 129, 76, 243, 171, 251, 97, 177, 102, 147, 223, 29, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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