Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05460267e029c46589373b4e6f87fa2e7e61e217eb4c5617c24f21c457ea8d98

Tx prefix hash: 0cea6a67e8b5cd3b883c08b9faa8f559c350974bf5e836034d1e71f617376d9c
Tx public key: ee647cab2c8279725902747173c2acab8d5d4da3ac4b9bb1aa77d4a3efa03527
Timestamp: 1698453513 Timestamp [UCT]: 2023-10-28 00:38:33 Age [y:d:h:m:s]: 01:017:10:23:19
Block: 879140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273633 RingCT/type: yes/0
Extra: 01ee647cab2c8279725902747173c2acab8d5d4da3ac4b9bb1aa77d4a3efa0352702110000000136a45730000000000000000000

1 output(s) for total of 0.749970612000 dcy

stealth address amount amount idx
00: b7c1864546adf87c6601095f6f3b36a0f5a750ca5798f2667b1c743ca27b3a58 0.749970612000 1334642 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": 879150, "vin": [ { "gen": { "height": 879140 } } ], "vout": [ { "amount": 749970612, "target": { "key": "b7c1864546adf87c6601095f6f3b36a0f5a750ca5798f2667b1c743ca27b3a58" } } ], "extra": [ 1, 238, 100, 124, 171, 44, 130, 121, 114, 89, 2, 116, 113, 115, 194, 172, 171, 141, 93, 77, 163, 172, 75, 155, 177, 170, 119, 212, 163, 239, 160, 53, 39, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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