Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7bc11523593a77d859b5b28b4e5990cc7449a5ce80d3cfe6a851bf484ae253

Tx prefix hash: 99fe4a9a3b74efabb813067e240e3d115ecf923188cf1df8ac5ef2552ee6f04f
Tx public key: a3f137c58eb1e897afce58bfb190407d0d70950e76aefe806cfcdde9c9a5fe47
Timestamp: 1709670531 Timestamp [UCT]: 2024-03-05 20:28:51 Age [y:d:h:m:s]: 01:104:22:00:53
Block: 971927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335897 RingCT/type: yes/0
Extra: 01a3f137c58eb1e897afce58bfb190407d0d70950e76aefe806cfcdde9c9a5fe4702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33f25f405ae7f4e7564006cf4eebc8b30e1d4de619735733e61fbc3acc85f465 0.600000000000 1431832 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": 971937, "vin": [ { "gen": { "height": 971927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33f25f405ae7f4e7564006cf4eebc8b30e1d4de619735733e61fbc3acc85f465" } } ], "extra": [ 1, 163, 241, 55, 197, 142, 177, 232, 151, 175, 206, 88, 191, 177, 144, 64, 125, 13, 112, 149, 14, 118, 174, 254, 128, 108, 252, 221, 233, 201, 165, 254, 71, 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