Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be119db2b85f05b7937e0303d3ed9f69f52356c387f3820e83a4bcb2ea1c19bc

Tx prefix hash: cd3b3bbf8c260580afac9155fbc5a36d1954f200920ed587b1a63c276d7e7771
Tx public key: 3e139367f5ce96889ff748c2016d5f896844b3785ed1e9e4c5aa6e7428449b38
Timestamp: 1713182758 Timestamp [UCT]: 2024-04-15 12:05:58 Age [y:d:h:m:s]: 01:209:20:04:53
Block: 1001031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408634 RingCT/type: yes/0
Extra: 013e139367f5ce96889ff748c2016d5f896844b3785ed1e9e4c5aa6e7428449b380211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368050def68e31c20f5582b366c882204fdb48dbef5d7e14fd4c8a3d281e3bfd 0.600000000000 1461533 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": 1001041, "vin": [ { "gen": { "height": 1001031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368050def68e31c20f5582b366c882204fdb48dbef5d7e14fd4c8a3d281e3bfd" } } ], "extra": [ 1, 62, 19, 147, 103, 245, 206, 150, 136, 159, 247, 72, 194, 1, 109, 95, 137, 104, 68, 179, 120, 94, 209, 233, 228, 197, 170, 110, 116, 40, 68, 155, 56, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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