Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 337a215091942bce3d8ecf9eb058e3267c7557e1bcff66f9d97534b90ed20aac

Tx prefix hash: d560860ac54a9ee769669418b2342b68331c50d7195accc3147e297edea524d7
Tx public key: 3a945e3389fe0211133aa2b51cc08c1d7eb8c7db71613fbba12546da27abc45b
Timestamp: 1730121806 Timestamp [UCT]: 2024-10-28 13:23:26 Age [y:d:h:m:s]: 00:238:18:25:54
Block: 1141396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170268 RingCT/type: yes/0
Extra: 013a945e3389fe0211133aa2b51cc08c1d7eb8c7db71613fbba12546da27abc45b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ce98ab7bf9d7e28513339534dcd3a6a7384b6d2e0b5b9a9515128f3a6c4d6bd 0.600000000000 1625203 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": 1141406, "vin": [ { "gen": { "height": 1141396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ce98ab7bf9d7e28513339534dcd3a6a7384b6d2e0b5b9a9515128f3a6c4d6bd" } } ], "extra": [ 1, 58, 148, 94, 51, 137, 254, 2, 17, 19, 58, 162, 181, 28, 192, 140, 29, 126, 184, 199, 219, 113, 97, 63, 187, 161, 37, 70, 218, 39, 171, 196, 91, 2, 17, 0, 0, 0, 2, 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