Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 078da3a61ac26c866e2e30cf131b440598f9c3678997a13fa1c5b07acdd42276

Tx prefix hash: 9d9c47861b9f02133ce5bb1c283c405f437f0b3267ff83c07417be0d9b8744ac
Tx public key: 5ee3003dfced190a7373abb1d67a68616e4d9e0b3bcd4165acf85b0cbf92b892
Timestamp: 1741290465 Timestamp [UCT]: 2025-03-06 19:47:45 Age [y:d:h:m:s]: 00:290:15:08:43
Block: 1233597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205503 RingCT/type: yes/0
Extra: 015ee3003dfced190a7373abb1d67a68616e4d9e0b3bcd4165acf85b0cbf92b89202110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b670b14236f23485da0b197b45d03a4e7b74b6bfb10e717c5d96e04cf943b6b 0.600000000000 1720520 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": 1233607, "vin": [ { "gen": { "height": 1233597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b670b14236f23485da0b197b45d03a4e7b74b6bfb10e717c5d96e04cf943b6b" } } ], "extra": [ 1, 94, 227, 0, 61, 252, 237, 25, 10, 115, 115, 171, 177, 214, 122, 104, 97, 110, 77, 158, 11, 59, 205, 65, 101, 172, 248, 91, 12, 191, 146, 184, 146, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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