Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d11ba16bf116ac802e86e95e8cf83ed5e66ed4c27a4a4f4ff7672921261e619

Tx prefix hash: 61b60fe03a0c154bdbdfbf2559859cd29449babbea8c62bd683d4d5908b0ba05
Tx public key: 0de28a29331fe8a26f37fce66cc3f3ede58a8079e9c6cefbde20d9e5a8dcc93d
Timestamp: 1735999065 Timestamp [UCT]: 2025-01-04 13:57:45 Age [y:d:h:m:s]: 00:101:23:03:41
Block: 1190070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72655 RingCT/type: yes/0
Extra: 010de28a29331fe8a26f37fce66cc3f3ede58a8079e9c6cefbde20d9e5a8dcc93d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ee34eb1f645147bec2aaf7c53a91f9b3208e00ed4f9993ee881649ee5c11ba1 0.600000000000 1676585 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": 1190080, "vin": [ { "gen": { "height": 1190070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ee34eb1f645147bec2aaf7c53a91f9b3208e00ed4f9993ee881649ee5c11ba1" } } ], "extra": [ 1, 13, 226, 138, 41, 51, 31, 232, 162, 111, 55, 252, 230, 108, 195, 243, 237, 229, 138, 128, 121, 233, 198, 206, 251, 222, 32, 217, 229, 168, 220, 201, 61, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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