Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601814f18ca756462d733688b5e9eca40876ea14cde320d81ead261e58383179

Tx prefix hash: a10479f262e9effce0fd791007c1de5ea72c60b2136bab088325db4e3af32a6a
Tx public key: fb8d6ffbb1a5a0d3a0b91bee5a9b744eb1c640c63ccf6159ee9e773643537995
Timestamp: 1702802642 Timestamp [UCT]: 2023-12-17 08:44:02 Age [y:d:h:m:s]: 01:123:10:35:49
Block: 914984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349362 RingCT/type: yes/0
Extra: 01fb8d6ffbb1a5a0d3a0b91bee5a9b744eb1c640c63ccf6159ee9e77364353799502110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6f83f6e7c8c19a290b7200509645d2c5ab28cf9790cf5064618b0f8fc9be2ef 0.600000000000 1372350 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": 914994, "vin": [ { "gen": { "height": 914984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6f83f6e7c8c19a290b7200509645d2c5ab28cf9790cf5064618b0f8fc9be2ef" } } ], "extra": [ 1, 251, 141, 111, 251, 177, 165, 160, 211, 160, 185, 27, 238, 90, 155, 116, 78, 177, 198, 64, 198, 60, 207, 97, 89, 238, 158, 119, 54, 67, 83, 121, 149, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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