Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1164b416845234a78ef9941512de8d534a61737b400840649d2356b1d40bba06

Tx prefix hash: 6234c38e3931d0af65e64e9220cd213dc14c20f0f0e4707e014d428ace4d58b0
Tx public key: a0b02e0d973f11ee81ffe83d106d49e8cdbbe15a3f29c04802d0bdb453e363c9
Timestamp: 1578653668 Timestamp [UCT]: 2020-01-10 10:54:28 Age [y:d:h:m:s]: 05:055:00:32:49
Block: 42533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189385 RingCT/type: yes/0
Extra: 01a0b02e0d973f11ee81ffe83d106d49e8cdbbe15a3f29c04802d0bdb453e363c902110000005bb221b3d1000000000000000000

1 output(s) for total of 443.681538958000 dcy

stealth address amount amount idx
00: a88c99ccefddc90d34aa54d72cf99cf95ba417e6f2d352ff1a5a3bd0f669865b 443.681538958000 76675 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": 42543, "vin": [ { "gen": { "height": 42533 } } ], "vout": [ { "amount": 443681538958, "target": { "key": "a88c99ccefddc90d34aa54d72cf99cf95ba417e6f2d352ff1a5a3bd0f669865b" } } ], "extra": [ 1, 160, 176, 46, 13, 151, 63, 17, 238, 129, 255, 232, 61, 16, 109, 73, 232, 205, 187, 225, 90, 63, 41, 192, 72, 2, 208, 189, 180, 83, 227, 99, 201, 2, 17, 0, 0, 0, 91, 178, 33, 179, 209, 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