Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed8166386da332f230d99d29a0822da551ccffb9926773e43f2d9c8b433cb1a

Tx prefix hash: 0b794e592f4609687c6d256f316e0a106cdae7cda09bf96bd2b343b482995fb7
Tx public key: bb380e35acf6369f00fbb8e7bcea67add365af894502e1a1fbf14e5f7e785306
Timestamp: 1578552903 Timestamp [UCT]: 2020-01-09 06:55:03 Age [y:d:h:m:s]: 05:032:01:52:43
Block: 41832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172846 RingCT/type: yes/0
Extra: 01bb380e35acf6369f00fbb8e7bcea67add365af894502e1a1fbf14e5f7e7853060211000000018a2ee0d9000000000000000000

1 output(s) for total of 446.060804841000 dcy

stealth address amount amount idx
00: a8d13efad3d29dbda127c5879e42eb26c0d4261467438e51c506049f2900ce33 446.060804841000 74965 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": 41842, "vin": [ { "gen": { "height": 41832 } } ], "vout": [ { "amount": 446060804841, "target": { "key": "a8d13efad3d29dbda127c5879e42eb26c0d4261467438e51c506049f2900ce33" } } ], "extra": [ 1, 187, 56, 14, 53, 172, 246, 54, 159, 0, 251, 184, 231, 188, 234, 103, 173, 211, 101, 175, 137, 69, 2, 225, 161, 251, 241, 78, 95, 126, 120, 83, 6, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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