Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 591390a427dc957326a44a393fadd37e82cb6ae35332830aa497807f572c126c

Tx prefix hash: 368b7d8eb45f36ee3eae6b97b4bb2ada009765ee5db8d5b7b8af62fae08c6345
Tx public key: e482f19c7bef9ab886baaaed28f53699a161a192d6418221227ab50511e41c4a
Timestamp: 1734354463 Timestamp [UCT]: 2024-12-16 13:07:43 Age [y:d:h:m:s]: 00:185:12:38:16
Block: 1176475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132266 RingCT/type: yes/0
Extra: 01e482f19c7bef9ab886baaaed28f53699a161a192d6418221227ab50511e41c4a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99265783fad0a50eb8efb20333a30f904cc6be0e0f7b721d5670b8b2b35771fe 0.600000000000 1662808 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": 1176485, "vin": [ { "gen": { "height": 1176475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99265783fad0a50eb8efb20333a30f904cc6be0e0f7b721d5670b8b2b35771fe" } } ], "extra": [ 1, 228, 130, 241, 156, 123, 239, 154, 184, 134, 186, 170, 237, 40, 245, 54, 153, 161, 97, 161, 146, 214, 65, 130, 33, 34, 122, 181, 5, 17, 228, 28, 74, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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