Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73651cec5bae3ccb5696d0ec29475504b530fc479a2f6140f6222a97f481057b

Tx prefix hash: 7075e255c5aaac7a914c4b8eb39f51476893c145446725d711e938503fadc0e2
Tx public key: 9f3531e4d18230ff9350f203ac3e8d53b514550c9042e9ffe0c35c3b3d155c66
Timestamp: 1726700614 Timestamp [UCT]: 2024-09-18 23:03:34 Age [y:d:h:m:s]: 00:070:11:15:30
Block: 1113109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50376 RingCT/type: yes/0
Extra: 019f3531e4d18230ff9350f203ac3e8d53b514550c9042e9ffe0c35c3b3d155c6602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e453359f0d1a576946e14256f25675c8a9fdc400a541f419a0c1dfa19788a90e 0.600000000000 1592664 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": 1113119, "vin": [ { "gen": { "height": 1113109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e453359f0d1a576946e14256f25675c8a9fdc400a541f419a0c1dfa19788a90e" } } ], "extra": [ 1, 159, 53, 49, 228, 209, 130, 48, 255, 147, 80, 242, 3, 172, 62, 141, 83, 181, 20, 85, 12, 144, 66, 233, 255, 224, 195, 92, 59, 61, 21, 92, 102, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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