Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367f0c08e0ca0df66470aafa6d8a53a50a0fc2bd6e6841eae992eb411da78523

Tx prefix hash: 39e77909047762b876ffe2e5c561b05ecd46b2b080b5e46808a25ebd684c7b04
Tx public key: fd59af8ce95a57efc35cc4323ae48bcdca83e94f95d58f0deae0bce80a92e647
Timestamp: 1706776913 Timestamp [UCT]: 2024-02-01 08:41:53 Age [y:d:h:m:s]: 01:077:05:49:28
Block: 947907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316297 RingCT/type: yes/0
Extra: 01fd59af8ce95a57efc35cc4323ae48bcdca83e94f95d58f0deae0bce80a92e6470211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73321d62162ce66de29881bf6164e12e4f52775c4c05007a15a5794fc0aef094 0.600000000000 1406267 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": 947917, "vin": [ { "gen": { "height": 947907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73321d62162ce66de29881bf6164e12e4f52775c4c05007a15a5794fc0aef094" } } ], "extra": [ 1, 253, 89, 175, 140, 233, 90, 87, 239, 195, 92, 196, 50, 58, 228, 139, 205, 202, 131, 233, 79, 149, 213, 143, 13, 234, 224, 188, 232, 10, 146, 230, 71, 2, 17, 0, 0, 0, 1, 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