Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 642d0195d7e8be26416c1757ca9727f8be1440bc7981fc19467d268793a53f3c

Tx prefix hash: be84f6fc3be0f0f354fd0dcc93b21e11a1ab1165595e46370129b291c6b4d568
Tx public key: fcb673e6283dd32110acf3afa0c628623cb0ee1acfa860fdc1df5d0af17699a1
Timestamp: 1725211836 Timestamp [UCT]: 2024-09-01 17:30:36 Age [y:d:h:m:s]: 01:069:01:24:10
Block: 1100765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307790 RingCT/type: yes/0
Extra: 01fcb673e6283dd32110acf3afa0c628623cb0ee1acfa860fdc1df5d0af17699a1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d5d9e6e930ecc3c7e193af745e9ba0e0da9e021a0af815dc571bac56819b9b2 0.600000000000 1576746 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": 1100775, "vin": [ { "gen": { "height": 1100765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d5d9e6e930ecc3c7e193af745e9ba0e0da9e021a0af815dc571bac56819b9b2" } } ], "extra": [ 1, 252, 182, 115, 230, 40, 61, 211, 33, 16, 172, 243, 175, 160, 198, 40, 98, 60, 176, 238, 26, 207, 168, 96, 253, 193, 223, 93, 10, 241, 118, 153, 161, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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