Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b381dbd99af0331578331c3db19f3c086dfb9fb7ca5c6732d01ed8e4e0fef6b2

Tx prefix hash: baf0a4bd6454b096d95eb08b8aac218430d97f2ead083e05f89004bf78bc441d
Tx public key: ce018b2d8380cf0e97c63ebcea32b218266dc20fc778b1ae6cfbf25b8950d4ed
Timestamp: 1705849653 Timestamp [UCT]: 2024-01-21 15:07:33 Age [y:d:h:m:s]: 01:292:11:42:10
Block: 940207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467865 RingCT/type: yes/0
Extra: 01ce018b2d8380cf0e97c63ebcea32b218266dc20fc778b1ae6cfbf25b8950d4ed0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3099d79bbd679b366539bbaa3a3d425e97654284dca720f0b37c72a7f60e0502 0.600000000000 1398341 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": 940217, "vin": [ { "gen": { "height": 940207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3099d79bbd679b366539bbaa3a3d425e97654284dca720f0b37c72a7f60e0502" } } ], "extra": [ 1, 206, 1, 139, 45, 131, 128, 207, 14, 151, 198, 62, 188, 234, 50, 178, 24, 38, 109, 194, 15, 199, 120, 177, 174, 108, 251, 242, 91, 137, 80, 212, 237, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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