Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de7d723cbeb56ba40623743d1c97dcd386cb52dba8f22ba6933aa0a160f37c1

Tx prefix hash: fed0edc7127956f702d534b8b95a44cc08868596e8ee3563ac60ffe05f364617
Tx public key: 8b4a2e1377832c4673bdcaa2485ed55e4029d5cdc411b666fcc1d36b3cbf1de1
Timestamp: 1704674120 Timestamp [UCT]: 2024-01-08 00:35:20 Age [y:d:h:m:s]: 01:049:22:33:18
Block: 930476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296772 RingCT/type: yes/0
Extra: 018b4a2e1377832c4673bdcaa2485ed55e4029d5cdc411b666fcc1d36b3cbf1de10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4d01fd8ea73a1485edb033b8840555edb6916c548da5d0aa7e42b358002dc0e 0.600000000000 1388358 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": 930486, "vin": [ { "gen": { "height": 930476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4d01fd8ea73a1485edb033b8840555edb6916c548da5d0aa7e42b358002dc0e" } } ], "extra": [ 1, 139, 74, 46, 19, 119, 131, 44, 70, 115, 189, 202, 162, 72, 94, 213, 94, 64, 41, 213, 205, 196, 17, 182, 102, 252, 193, 211, 107, 60, 191, 29, 225, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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