Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76649e069cc0a34a2de18994c50c4fe46d63c8dfb0587e516047eadc76ffc8c5

Tx prefix hash: 250ffe9120140ba99292495cfe880c5a4334a0fc27170323a6a732a2b011d586
Tx public key: 9ce3afe907d9502e464c3a308491dfc6f1eac311c547a88fd07f71c31f292160
Timestamp: 1706980617 Timestamp [UCT]: 2024-02-03 17:16:57 Age [y:d:h:m:s]: 01:280:00:12:37
Block: 949604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458913 RingCT/type: yes/0
Extra: 019ce3afe907d9502e464c3a308491dfc6f1eac311c547a88fd07f71c31f2921600211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b74e6889175f4e84a84ad09ae000be36fe4d5935406a3de231ff592031ab742 0.600000000000 1408134 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": 949614, "vin": [ { "gen": { "height": 949604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b74e6889175f4e84a84ad09ae000be36fe4d5935406a3de231ff592031ab742" } } ], "extra": [ 1, 156, 227, 175, 233, 7, 217, 80, 46, 70, 76, 58, 48, 132, 145, 223, 198, 241, 234, 195, 17, 197, 71, 168, 143, 208, 127, 113, 195, 31, 41, 33, 96, 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