Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862aa13aeb2189391691cfe16593ed39bae9578df27e716bf1ca06ff92f580d3

Tx prefix hash: d60d33463dd72ee2f1c761333e24a0000d945d28d0acfd29cb32d12daa85fc64
Tx public key: 008b4677b0e3503a2b20bb1f5be4fd422a21311484e5397c6feca60ff8c950ac
Timestamp: 1635035142 Timestamp [UCT]: 2021-10-24 00:25:42 Age [y:d:h:m:s]: 04:008:04:42:27
Block: 359163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1042553 RingCT/type: yes/0
Extra: 01008b4677b0e3503a2b20bb1f5be4fd422a21311484e5397c6feca60ff8c950ac0211000000105410958b000000000000000000

1 output(s) for total of 39.623410918000 dcy

stealth address amount amount idx
00: 231b1d37d7ca9770a257a1a372bfded501795805b497506ef249cc9868d4fb64 39.623410918000 731516 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": 359173, "vin": [ { "gen": { "height": 359163 } } ], "vout": [ { "amount": 39623410918, "target": { "key": "231b1d37d7ca9770a257a1a372bfded501795805b497506ef249cc9868d4fb64" } } ], "extra": [ 1, 0, 139, 70, 119, 176, 227, 80, 58, 43, 32, 187, 31, 91, 228, 253, 66, 42, 33, 49, 20, 132, 229, 57, 124, 111, 236, 166, 15, 248, 201, 80, 172, 2, 17, 0, 0, 0, 16, 84, 16, 149, 139, 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