Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f15c3cf3c027c78699787b19ec36c303587a423636acc59326759b15498ef953

Tx prefix hash: 29e55a2617090509478641ba6448c6e7c26726bf626d6591599f25b8895cf6fd
Tx public key: c8dfaf6c3ef8b6efe72a4f310c50bb2a47e5d8fd907aa1575428c359ce05311a
Timestamp: 1713950882 Timestamp [UCT]: 2024-04-24 09:28:02 Age [y:d:h:m:s]: 01:224:12:33:46
Block: 1007408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419153 RingCT/type: yes/0
Extra: 01c8dfaf6c3ef8b6efe72a4f310c50bb2a47e5d8fd907aa1575428c359ce05311a021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e878637e2ba86e1689d86ec89613519d14820bed370a6e21d36a4c40dc9e1211 0.600000000000 1468740 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": 1007418, "vin": [ { "gen": { "height": 1007408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e878637e2ba86e1689d86ec89613519d14820bed370a6e21d36a4c40dc9e1211" } } ], "extra": [ 1, 200, 223, 175, 108, 62, 248, 182, 239, 231, 42, 79, 49, 12, 80, 187, 42, 71, 229, 216, 253, 144, 122, 161, 87, 84, 40, 195, 89, 206, 5, 49, 26, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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