Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0944ee6f5822a88fef0b3e27f77aded2a65d130b6a394884f2e8afdfd29eb264

Tx prefix hash: ee3c0329b57b013b35a84070a8576a642b9606e8fa1bac45e614b4f08e6bc127
Tx public key: b7a00d926c807fe687f42b5eefce752c502ec98dc46194bd1f40761dacdaf5c4
Timestamp: 1736049648 Timestamp [UCT]: 2025-01-05 04:00:48 Age [y:d:h:m:s]: 00:098:20:08:45
Block: 1190485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70442 RingCT/type: yes/0
Extra: 01b7a00d926c807fe687f42b5eefce752c502ec98dc46194bd1f40761dacdaf5c4021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d8bf80699e8b70d82c65045942bf46e81d32ef50cec4f6327fd781e89aab1cb 0.600000000000 1677002 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": 1190495, "vin": [ { "gen": { "height": 1190485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d8bf80699e8b70d82c65045942bf46e81d32ef50cec4f6327fd781e89aab1cb" } } ], "extra": [ 1, 183, 160, 13, 146, 108, 128, 127, 230, 135, 244, 43, 94, 239, 206, 117, 44, 80, 46, 201, 141, 196, 97, 148, 189, 31, 64, 118, 29, 172, 218, 245, 196, 2, 17, 0, 0, 0, 5, 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