Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3328abdc234d06ac404b75513c79e8ba38cf41449c576c99622f5d3131f6d2

Tx prefix hash: a27d4d4fc43ac0cbff49fd98fbcd2ee470b678f3906aeced7ea28848c0b33122
Tx public key: 5904ce375e63eb34aa590de5e0c3566bdb5108ca0dc6995858cefbc4bbcb7408
Timestamp: 1712587113 Timestamp [UCT]: 2024-04-08 14:38:33 Age [y:d:h:m:s]: 01:019:04:08:58
Block: 996068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274696 RingCT/type: yes/0
Extra: 015904ce375e63eb34aa590de5e0c3566bdb5108ca0dc6995858cefbc4bbcb740802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6eae591e218de934d1a257f5a098231fb213f06318c0e71bcd45c4868ac53f7 0.600000000000 1456484 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": 996078, "vin": [ { "gen": { "height": 996068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6eae591e218de934d1a257f5a098231fb213f06318c0e71bcd45c4868ac53f7" } } ], "extra": [ 1, 89, 4, 206, 55, 94, 99, 235, 52, 170, 89, 13, 229, 224, 195, 86, 107, 219, 81, 8, 202, 13, 198, 153, 88, 88, 206, 251, 196, 187, 203, 116, 8, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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