Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdceb61253db1c9c636291ed9f0e9b0d55763979277c7515a43ff6afc937679f

Tx prefix hash: a6728d843e5a5430bce4f4317098cff9e814d7d6d15f5bbc998e85838de885c2
Tx public key: 6a67564836ed053173cf4dbb4b8820e773f94316ecbd2e58ead199a4891aab2b
Timestamp: 1726799268 Timestamp [UCT]: 2024-09-20 02:27:48 Age [y:d:h:m:s]: 01:060:01:07:16
Block: 1113919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301338 RingCT/type: yes/0
Extra: 016a67564836ed053173cf4dbb4b8820e773f94316ecbd2e58ead199a4891aab2b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51288edf4a282c98c9946d0e418a295a25f5dc11bb287f18abe0a86c6b66ee9f 0.600000000000 1593716 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": 1113929, "vin": [ { "gen": { "height": 1113919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51288edf4a282c98c9946d0e418a295a25f5dc11bb287f18abe0a86c6b66ee9f" } } ], "extra": [ 1, 106, 103, 86, 72, 54, 237, 5, 49, 115, 207, 77, 187, 75, 136, 32, 231, 115, 249, 67, 22, 236, 189, 46, 88, 234, 209, 153, 164, 137, 26, 171, 43, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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