Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cd120b354381199cb62000bf5c4d38fc3d9e6c03bae64aab9017e214e05bd6b

Tx prefix hash: 27976237c5e1d380ce455cd57bee584c896c2e7b0be5dddb1843fa0823022821
Tx public key: 4e9abf683da0066b5708410cf06ce2f32a9252c7a6c67715101317f9e20185e0
Timestamp: 1722514922 Timestamp [UCT]: 2024-08-01 12:22:02 Age [y:d:h:m:s]: 00:119:00:08:50
Block: 1078406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85150 RingCT/type: yes/0
Extra: 014e9abf683da0066b5708410cf06ce2f32a9252c7a6c67715101317f9e20185e0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c6ed4caff6a030f8bcd366ef4aa3ff73fe8ecd61fe3975a2567e4d5c3b6a3c9 0.600000000000 1550983 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": 1078416, "vin": [ { "gen": { "height": 1078406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c6ed4caff6a030f8bcd366ef4aa3ff73fe8ecd61fe3975a2567e4d5c3b6a3c9" } } ], "extra": [ 1, 78, 154, 191, 104, 61, 160, 6, 107, 87, 8, 65, 12, 240, 108, 226, 243, 42, 146, 82, 199, 166, 198, 119, 21, 16, 19, 23, 249, 226, 1, 133, 224, 2, 17, 0, 0, 0, 6, 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