Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d76566e20ee983fce96b6808eebc5d97902d3fd78e4b184343b8e513e048a89

Tx prefix hash: bbe0789df2db57e25ae1256aefc414a4286bb70ea7db3e5729b12867bd1356ec
Tx public key: 1e076139b17b7536ed71f944a38a3fa30433ad0237671505a0f8e4c8c0b90b63
Timestamp: 1699537594 Timestamp [UCT]: 2023-11-09 13:46:34 Age [y:d:h:m:s]: 01:131:08:32:35
Block: 887927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355071 RingCT/type: yes/0
Extra: 011e076139b17b7536ed71f944a38a3fa30433ad0237671505a0f8e4c8c0b90b630211000000094b8f5122000000000000000000

1 output(s) for total of 0.701341042000 dcy

stealth address amount amount idx
00: 03f9a671db36878661af25bce562a8639560c5d70bcb6c2e1383810693639162 0.701341042000 1343836 of 0

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": 887937, "vin": [ { "gen": { "height": 887927 } } ], "vout": [ { "amount": 701341042, "target": { "key": "03f9a671db36878661af25bce562a8639560c5d70bcb6c2e1383810693639162" } } ], "extra": [ 1, 30, 7, 97, 57, 177, 123, 117, 54, 237, 113, 249, 68, 163, 138, 63, 163, 4, 51, 173, 2, 55, 103, 21, 5, 160, 248, 228, 200, 192, 185, 11, 99, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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