Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bee19a67d3ffaeb58292e2ea9ffeaa449dc4470e3a51fa46e3f6485101a27e7f

Tx prefix hash: de5b764922728c9e2d1ceb75436f2d3a829abb1c2cb713097012bf88a9b89000
Tx public key: caf3613b5f91735e8628e23313d74d64cf59fce7fcb10c82dc8a2d49cd2d283a
Timestamp: 1706206264 Timestamp [UCT]: 2024-01-25 18:11:04 Age [y:d:h:m:s]: 00:351:12:02:08
Block: 943165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251682 RingCT/type: yes/0
Extra: 01caf3613b5f91735e8628e23313d74d64cf59fce7fcb10c82dc8a2d49cd2d283a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 081b59b53ee1205652ee3bc04cde1ba313447ea4620cf2d901d615cbccbfb56b 0.600000000000 1401365 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": 943175, "vin": [ { "gen": { "height": 943165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "081b59b53ee1205652ee3bc04cde1ba313447ea4620cf2d901d615cbccbfb56b" } } ], "extra": [ 1, 202, 243, 97, 59, 95, 145, 115, 94, 134, 40, 226, 51, 19, 215, 77, 100, 207, 89, 252, 231, 252, 177, 12, 130, 220, 138, 45, 73, 205, 45, 40, 58, 2, 17, 0, 0, 0, 6, 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