Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c13f8b55112cf3935816ff4c050e9aa9a470d88c952c7a1e513133d594b61b52

Tx prefix hash: 54d28d9951763dbb846eb8e3c003a0cb6c301e303c3ed04480ed8634fc7897d8
Tx public key: 6e8291cec8e173326441306acc574e53c3f3f963f7d6ae9ce671804ffc57a684
Timestamp: 1732341650 Timestamp [UCT]: 2024-11-23 06:00:50 Age [y:d:h:m:s]: 00:000:23:08:12
Block: 1159768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698 RingCT/type: yes/0
Extra: 016e8291cec8e173326441306acc574e53c3f3f963f7d6ae9ce671804ffc57a684021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dabffc7bae66b106255b7f7eb463ff8c78bc1edfd55f857e2fb7d263af21cf31 0.600000000000 1645407 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": 1159778, "vin": [ { "gen": { "height": 1159768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dabffc7bae66b106255b7f7eb463ff8c78bc1edfd55f857e2fb7d263af21cf31" } } ], "extra": [ 1, 110, 130, 145, 206, 200, 225, 115, 50, 100, 65, 48, 106, 204, 87, 78, 83, 195, 243, 249, 99, 247, 214, 174, 156, 230, 113, 128, 79, 252, 87, 166, 132, 2, 17, 0, 0, 0, 2, 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