Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ab6565b48a4d82976cf531d2e4d923749f8f3adac857b41cb1937a1c453cf6

Tx prefix hash: affb6c9d00de9144449a4ef77575dc287affcb9b454886e790f73238a560900a
Tx public key: 16d512fd4558b5caef07c9f7edaa917e1b7d253d9d1095d8a9ba42343a5576e0
Timestamp: 1577174718 Timestamp [UCT]: 2019-12-24 08:05:18 Age [y:d:h:m:s]: 05:072:01:35:37
Block: 30514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201354 RingCT/type: yes/0
Extra: 0116d512fd4558b5caef07c9f7edaa917e1b7d253d9d1095d8a9ba42343a5576e00211000000034ac5aa02000000000000000000

1 output(s) for total of 486.333540528000 dcy

stealth address amount amount idx
00: 82d7d10edc44933c1eae00ef8e0a97b43fdefcf0de29dc1e920c46cf560f0f1b 486.333540528000 50384 of 0

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": 30524, "vin": [ { "gen": { "height": 30514 } } ], "vout": [ { "amount": 486333540528, "target": { "key": "82d7d10edc44933c1eae00ef8e0a97b43fdefcf0de29dc1e920c46cf560f0f1b" } } ], "extra": [ 1, 22, 213, 18, 253, 69, 88, 181, 202, 239, 7, 201, 247, 237, 170, 145, 126, 27, 125, 37, 61, 157, 16, 149, 216, 169, 186, 66, 52, 58, 85, 118, 224, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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