Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f0753b4292544ca0d68b47f9349afd6b73c6a6f4af09592ecf1b053f7ac4c0

Tx prefix hash: 58a19aeaf1006c1bdddbb077c3a8d46eae3db7669161927dc817826a9817fcea
Tx public key: 177d26c705f3fb0f2db70a34fe975af5fb07150250e1ee717f3d6586f76b90ba
Timestamp: 1716488975 Timestamp [UCT]: 2024-05-23 18:29:35 Age [y:d:h:m:s]: 00:328:22:33:31
Block: 1028451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235100 RingCT/type: yes/0
Extra: 01177d26c705f3fb0f2db70a34fe975af5fb07150250e1ee717f3d6586f76b90ba02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03235cfcd62242c68f43d4aefcf1d99886f3629cb6f7e0c02e5563dcac144ce2 0.600000000000 1496444 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": 1028461, "vin": [ { "gen": { "height": 1028451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03235cfcd62242c68f43d4aefcf1d99886f3629cb6f7e0c02e5563dcac144ce2" } } ], "extra": [ 1, 23, 125, 38, 199, 5, 243, 251, 15, 45, 183, 10, 52, 254, 151, 90, 245, 251, 7, 21, 2, 80, 225, 238, 113, 127, 61, 101, 134, 247, 107, 144, 186, 2, 17, 0, 0, 0, 1, 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