Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23a1475c66894a813a9cb088a5d4e2b493ad1ee04f64c9dca7087749390c419

Tx prefix hash: e04e6a0bb2d28d51c457b1f548c3cd5cc453dfdf508c068f02cba7d9e129431c
Tx public key: 39346820f7bf4a3343f874344e16afb47fd57d9f5eac1d8a944a1f6a0661ae96
Timestamp: 1608414419 Timestamp [UCT]: 2020-12-19 21:46:59 Age [y:d:h:m:s]: 04:071:12:52:45
Block: 165412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1063607 RingCT/type: yes/0
Extra: 0139346820f7bf4a3343f874344e16afb47fd57d9f5eac1d8a944a1f6a0661ae960211000002a34ea414e5000000000000000000

1 output(s) for total of 173.754914782000 dcy

stealth address amount amount idx
00: bf300a5164ef799f722c76a9b26ea36fe418ac48911eeec8cea2bc0cdab0e2ff 173.754914782000 300971 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": 165422, "vin": [ { "gen": { "height": 165412 } } ], "vout": [ { "amount": 173754914782, "target": { "key": "bf300a5164ef799f722c76a9b26ea36fe418ac48911eeec8cea2bc0cdab0e2ff" } } ], "extra": [ 1, 57, 52, 104, 32, 247, 191, 74, 51, 67, 248, 116, 52, 78, 22, 175, 180, 127, 213, 125, 159, 94, 172, 29, 138, 148, 74, 31, 106, 6, 97, 174, 150, 2, 17, 0, 0, 2, 163, 78, 164, 20, 229, 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