Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa951a5f0515173b5b978e8d05e43186341dc452f46106f3fcc967808b2e43d

Tx prefix hash: 5e3d29653fadc1666513ab5d91b04b28d0f1c10bc1e8dd8a44fc22846999f893
Tx public key: 57c70f3c54130049720fcd21a490663607ea28f3c6e8c949316c0513e2963e67
Timestamp: 1738151477 Timestamp [UCT]: 2025-01-29 11:51:17 Age [y:d:h:m:s]: 00:296:14:12:10
Block: 1207616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209734 RingCT/type: yes/0
Extra: 0157c70f3c54130049720fcd21a490663607ea28f3c6e8c949316c0513e2963e6702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dadb4f64e923bd9fd2b1b2a0e5b91e4a9bd0b3fa9901cda7f9375832885209d 0.600000000000 1694341 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": 1207626, "vin": [ { "gen": { "height": 1207616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dadb4f64e923bd9fd2b1b2a0e5b91e4a9bd0b3fa9901cda7f9375832885209d" } } ], "extra": [ 1, 87, 199, 15, 60, 84, 19, 0, 73, 114, 15, 205, 33, 164, 144, 102, 54, 7, 234, 40, 243, 198, 232, 201, 73, 49, 108, 5, 19, 226, 150, 62, 103, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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