Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85966af8d6834085b85938b8b44b8dc2617490f05f04b9285a27c6acfb7cead9

Tx prefix hash: 4080a99de7b83783a3bcf32a7b639d20e2cc3c96a63bdc4d644f7dd7ed18cfba
Tx public key: 3b5dfc48730d234c80d9134cf92b348a26bc6f250b7f042b8c6080e4386450df
Timestamp: 1702884332 Timestamp [UCT]: 2023-12-18 07:25:32 Age [y:d:h:m:s]: 01:339:04:37:37
Block: 915659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501275 RingCT/type: yes/0
Extra: 013b5dfc48730d234c80d9134cf92b348a26bc6f250b7f042b8c6080e4386450df02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 767368675545b806917179ab4812e7ccff352fd24f416d266d0a1c773796b9e7 0.600000000000 1373055 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": 915669, "vin": [ { "gen": { "height": 915659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "767368675545b806917179ab4812e7ccff352fd24f416d266d0a1c773796b9e7" } } ], "extra": [ 1, 59, 93, 252, 72, 115, 13, 35, 76, 128, 217, 19, 76, 249, 43, 52, 138, 38, 188, 111, 37, 11, 127, 4, 43, 140, 96, 128, 228, 56, 100, 80, 223, 2, 17, 0, 0, 0, 1, 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