Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b1c5ff8c5a58f97291c63d27776ca9e62560c14001a99aa1255a1d444e234f9

Tx prefix hash: c2d3515866cda783ec5566b19bb4d86942dde859fa2daf4126654b92e6f99218
Tx public key: 0dcca1a05ae6df25c731b2cb7d9a8eef1a9198bd515c4e4cd81adef0f45ae7c4
Timestamp: 1749628103 Timestamp [UCT]: 2025-06-11 07:48:23 Age [y:d:h:m:s]: 00:152:11:57:19
Block: 1302621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106677 RingCT/type: yes/0
Extra: 010dcca1a05ae6df25c731b2cb7d9a8eef1a9198bd515c4e4cd81adef0f45ae7c4021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a82186a34034e307ba2b6b849356e318eb0a865e6aba156efff17832abdb10f 0.600000000000 1790192 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": 1302631, "vin": [ { "gen": { "height": 1302621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a82186a34034e307ba2b6b849356e318eb0a865e6aba156efff17832abdb10f" } } ], "extra": [ 1, 13, 204, 161, 160, 90, 230, 223, 37, 199, 49, 178, 203, 125, 154, 142, 239, 26, 145, 152, 189, 81, 92, 78, 76, 216, 26, 222, 240, 244, 90, 231, 196, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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