Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de8529279b96e2f995c3d06dfc19e61c6cffac1d4610255b72b4475806d74a9

Tx prefix hash: 2b3174315918bbbab04cef96f9b3b6459fbc95c5aa6be8c72166f19bce0b19e8
Tx public key: 8d2f01c3c6b1b040e4af582d5e21abd5e547bd654a40721f4e56668552a9c167
Timestamp: 1737546449 Timestamp [UCT]: 2025-01-22 11:47:29 Age [y:d:h:m:s]: 00:297:10:58:00
Block: 1202828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210140 RingCT/type: yes/0
Extra: 018d2f01c3c6b1b040e4af582d5e21abd5e547bd654a40721f4e56668552a9c167021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15244c2a76588ca2a9f87f6f7894c3e4e77d3e5339cabe6c9d66658d128c4de6 0.600000000000 1689495 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": 1202838, "vin": [ { "gen": { "height": 1202828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15244c2a76588ca2a9f87f6f7894c3e4e77d3e5339cabe6c9d66658d128c4de6" } } ], "extra": [ 1, 141, 47, 1, 195, 198, 177, 176, 64, 228, 175, 88, 45, 94, 33, 171, 213, 229, 71, 189, 101, 74, 64, 114, 31, 78, 86, 102, 133, 82, 169, 193, 103, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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