Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17a32ba2fc6edef8d575ab3c33c82b33afa8269eb873384cff20ef486278ac38

Tx prefix hash: 7a3d72a2beda5f0db44ae1fefb199824d7a867de885a0439c36acd4fc607a4ca
Tx public key: b2a276a3f540ccb8636046dca9c2df5ff41f543325d5f656b7218b5afcd9e8ba
Timestamp: 1705238185 Timestamp [UCT]: 2024-01-14 13:16:25 Age [y:d:h:m:s]: 01:075:03:51:19
Block: 935164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314807 RingCT/type: yes/0
Extra: 01b2a276a3f540ccb8636046dca9c2df5ff41f543325d5f656b7218b5afcd9e8ba0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 414b7ab1694c8c69e899c49473a37a329cbbed35fa85112065fff8888d2a0451 0.600000000000 1393180 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": 935174, "vin": [ { "gen": { "height": 935164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "414b7ab1694c8c69e899c49473a37a329cbbed35fa85112065fff8888d2a0451" } } ], "extra": [ 1, 178, 162, 118, 163, 245, 64, 204, 184, 99, 96, 70, 220, 169, 194, 223, 95, 244, 31, 84, 51, 37, 213, 246, 86, 183, 33, 139, 90, 252, 217, 232, 186, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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