Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b2478b1208a9c8584735e0f2acdb2b220899186f4efcf774446ed5863bdb59c

Tx prefix hash: aa849037343f9e2a32900b7a4334ba532ab79dea23a9df59e12545c815cbdaca
Tx public key: a89b3212a9fc3d3d991e38851b8c5f5759159f89efcb171f03e734a4f30e777a
Timestamp: 1725121848 Timestamp [UCT]: 2024-08-31 16:30:48 Age [y:d:h:m:s]: 00:206:17:37:39
Block: 1100010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147594 RingCT/type: yes/0
Extra: 01a89b3212a9fc3d3d991e38851b8c5f5759159f89efcb171f03e734a4f30e777a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e3d9a091aff3def225f96a8d8c14fa53e43040198912f4ea8fd66d20dae6e2a 0.600000000000 1575981 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": 1100020, "vin": [ { "gen": { "height": 1100010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e3d9a091aff3def225f96a8d8c14fa53e43040198912f4ea8fd66d20dae6e2a" } } ], "extra": [ 1, 168, 155, 50, 18, 169, 252, 61, 61, 153, 30, 56, 133, 27, 140, 95, 87, 89, 21, 159, 137, 239, 203, 23, 31, 3, 231, 52, 164, 243, 14, 119, 122, 2, 17, 0, 0, 0, 3, 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