Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d799fc089697987e3ded611cba213095f721dd0e2734a5eadc49e21e69e58a9e

Tx prefix hash: 766df8859d2a9b845baac929325bfb6034fde912fd8ac93039e170e17c775669
Tx public key: bb95d503e41a4fbe90b98be70e60f2296d97f70a3e31ed0a5ffb210871267b42
Timestamp: 1718648882 Timestamp [UCT]: 2024-06-17 18:28:02 Age [y:d:h:m:s]: 00:290:07:29:41
Block: 1046356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207444 RingCT/type: yes/0
Extra: 01bb95d503e41a4fbe90b98be70e60f2296d97f70a3e31ed0a5ffb210871267b420211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 523ed819de2af1b7745cb25d93c22e20c4ce617fd1e1318cfdca6d67575a66b5 0.600000000000 1516167 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": 1046366, "vin": [ { "gen": { "height": 1046356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "523ed819de2af1b7745cb25d93c22e20c4ce617fd1e1318cfdca6d67575a66b5" } } ], "extra": [ 1, 187, 149, 213, 3, 228, 26, 79, 190, 144, 185, 139, 231, 14, 96, 242, 41, 109, 151, 247, 10, 62, 49, 237, 10, 95, 251, 33, 8, 113, 38, 123, 66, 2, 17, 0, 0, 0, 1, 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