Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee200f34d741178760606ac5f4849a806c41f8de734ab517e966585db289cde5

Tx prefix hash: 646cd2d51d78954ef1dd9fba38e6a334dc0d57726ea9c1906636937d23ad09fd
Tx public key: cd82733f07b7fdb95725c3ed458b35d3a9714879e0d756767bb0c7f78d04d394
Timestamp: 1634862873 Timestamp [UCT]: 2021-10-22 00:34:33 Age [y:d:h:m:s]: 03:143:19:01:50
Block: 357745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 880876 RingCT/type: yes/0
Extra: 01cd82733f07b7fdb95725c3ed458b35d3a9714879e0d756767bb0c7f78d04d3940211000000030bff1318000000000000000000

1 output(s) for total of 40.053707339000 dcy

stealth address amount amount idx
00: 9c855a9ad4d8a0ef3bca9eea1c847816e02ceb3d4c0b8288350bf084ea3d0fde 40.053707339000 729339 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": 357755, "vin": [ { "gen": { "height": 357745 } } ], "vout": [ { "amount": 40053707339, "target": { "key": "9c855a9ad4d8a0ef3bca9eea1c847816e02ceb3d4c0b8288350bf084ea3d0fde" } } ], "extra": [ 1, 205, 130, 115, 63, 7, 183, 253, 185, 87, 37, 195, 237, 69, 139, 53, 211, 169, 113, 72, 121, 224, 215, 86, 118, 123, 176, 199, 247, 141, 4, 211, 148, 2, 17, 0, 0, 0, 3, 11, 255, 19, 24, 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