Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75d99b9493c229eb464996a0cc775fa7f655ca022a2876fb2e039adbe319ad6c

Tx prefix hash: c1f714bcba2004d82c807fd45e14ccac4d797e4935d4144a0763c18afe72c211
Tx public key: f737f34105668bf5c5bb8a888196b8b71dfa2b9c30536eb0f1c9262a6c4c24f1
Timestamp: 1731873003 Timestamp [UCT]: 2024-11-17 19:50:03 Age [y:d:h:m:s]: 00:184:12:11:00
Block: 1155906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131718 RingCT/type: yes/0
Extra: 01f737f34105668bf5c5bb8a888196b8b71dfa2b9c30536eb0f1c9262a6c4c24f10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40f040ab0a4cb8bc15d903ff9dde3579f2db269c4952ffb5463067480e0253f4 0.600000000000 1641525 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": 1155916, "vin": [ { "gen": { "height": 1155906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40f040ab0a4cb8bc15d903ff9dde3579f2db269c4952ffb5463067480e0253f4" } } ], "extra": [ 1, 247, 55, 243, 65, 5, 102, 139, 245, 197, 187, 138, 136, 129, 150, 184, 183, 29, 250, 43, 156, 48, 83, 110, 176, 241, 201, 38, 42, 108, 76, 36, 241, 2, 17, 0, 0, 0, 3, 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