Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ec669408474e35a7cfcfc23604e38eaae121f824e257695933e71c54ba24169

Tx prefix hash: badcbef331e4d6c607bd4e8c4a5d8d9235cffd7c45d1f4a22c6b5383107b1a88
Tx public key: 9096150cfb073f6eb302b42f98e4a58dce70fbc18bd206976524fa9d039b48bc
Timestamp: 1725523414 Timestamp [UCT]: 2024-09-05 08:03:34 Age [y:d:h:m:s]: 01:064:19:18:41
Block: 1103346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304744 RingCT/type: yes/0
Extra: 019096150cfb073f6eb302b42f98e4a58dce70fbc18bd206976524fa9d039b48bc021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fd250b906a2d3b61ca5eed8f611c42b3bfbeddafab2ad771c02d58cdd48f97e 0.600000000000 1580141 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": 1103356, "vin": [ { "gen": { "height": 1103346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fd250b906a2d3b61ca5eed8f611c42b3bfbeddafab2ad771c02d58cdd48f97e" } } ], "extra": [ 1, 144, 150, 21, 12, 251, 7, 63, 110, 179, 2, 180, 47, 152, 228, 165, 141, 206, 112, 251, 193, 139, 210, 6, 151, 101, 36, 250, 157, 3, 155, 72, 188, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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