Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9817d0283fa12e2d9bc4aabc4be76b6d469ddebc28300803a0ec17409da94808

Tx prefix hash: 253cee7c813c025071dc67a7a0b04c1fbce9f1ed5f8323958e528c0245a8ac56
Tx public key: 396fd3a5e996d7ea56fa8b9fc776750b05ac44b99e86b85c790f6217919a6521
Timestamp: 1713963634 Timestamp [UCT]: 2024-04-24 13:00:34 Age [y:d:h:m:s]: 01:034:14:25:59
Block: 1007518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285691 RingCT/type: yes/0
Extra: 01396fd3a5e996d7ea56fa8b9fc776750b05ac44b99e86b85c790f6217919a652102110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f51d2d5336df9c724a65515c39019b5b7baeb6d12027b59cf349c3d1d1f8fc89 0.600000000000 1468884 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": 1007528, "vin": [ { "gen": { "height": 1007518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f51d2d5336df9c724a65515c39019b5b7baeb6d12027b59cf349c3d1d1f8fc89" } } ], "extra": [ 1, 57, 111, 211, 165, 233, 150, 215, 234, 86, 250, 139, 159, 199, 118, 117, 11, 5, 172, 68, 185, 158, 134, 184, 92, 121, 15, 98, 23, 145, 154, 101, 33, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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