Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d041625b993ba759f084f1dad0c47a0f0e39b0df3db2a1981b853c076960cf86

Tx prefix hash: e7a373e29a6b69e4a749ad37fe4b377cc771629302b2ba3d37d16fd2fe86e33d
Tx public key: 44ac2d11c7aaf9b01c04f536ab135c6de5a0bf1cf6cc9b2bb77ea8efcaed82a4
Timestamp: 1726130820 Timestamp [UCT]: 2024-09-12 08:47:00 Age [y:d:h:m:s]: 00:215:00:46:15
Block: 1108375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153534 RingCT/type: yes/0
Extra: 0144ac2d11c7aaf9b01c04f536ab135c6de5a0bf1cf6cc9b2bb77ea8efcaed82a4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e87b2fdfa741443cdb772d2bbdeeb6ee83db1e8b06024e036a6fab1f5b7c2454 0.600000000000 1586250 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": 1108385, "vin": [ { "gen": { "height": 1108375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e87b2fdfa741443cdb772d2bbdeeb6ee83db1e8b06024e036a6fab1f5b7c2454" } } ], "extra": [ 1, 68, 172, 45, 17, 199, 170, 249, 176, 28, 4, 245, 54, 171, 19, 92, 109, 229, 160, 191, 28, 246, 204, 155, 43, 183, 126, 168, 239, 202, 237, 130, 164, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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