Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3595251b979f0f8b93a2773d378d9194dcc56e9011944d9911cb2e81445f41

Tx prefix hash: 408bbac0d7dff35cae852db1b758bee1c221bc4ba32daaf714d41f34114a58ba
Tx public key: ed381f94aeecaea7a2e1cb18e9808b3ea3d87a5caa99ed32a5ff83ce3301e1a4
Timestamp: 1731664797 Timestamp [UCT]: 2024-11-15 09:59:57 Age [y:d:h:m:s]: 00:145:18:19:08
Block: 1154172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104004 RingCT/type: yes/0
Extra: 01ed381f94aeecaea7a2e1cb18e9808b3ea3d87a5caa99ed32a5ff83ce3301e1a40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4774f29d4c2fdf0072541a3ec2da9274e15735941ac29cc36ab789fda195639f 0.600000000000 1639783 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": 1154182, "vin": [ { "gen": { "height": 1154172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4774f29d4c2fdf0072541a3ec2da9274e15735941ac29cc36ab789fda195639f" } } ], "extra": [ 1, 237, 56, 31, 148, 174, 236, 174, 167, 162, 225, 203, 24, 233, 128, 139, 62, 163, 216, 122, 92, 170, 153, 237, 50, 165, 255, 131, 206, 51, 1, 225, 164, 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