Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86414fe28e7b9a1ff550c2659d02efc7e56a322d72f42fec0b4b17579f4a2f8c

Tx prefix hash: 9eabc988b269ba4481c0616c75e376f4a7c830ddde599b1e4f9aa241d9f70f35
Tx public key: a4c942948ae768e8d995f4a0540be2c08a9e25457a03c9cb07b4e71e12853d06
Timestamp: 1734892607 Timestamp [UCT]: 2024-12-22 18:36:47 Age [y:d:h:m:s]: 00:123:00:50:53
Block: 1180933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87707 RingCT/type: yes/0
Extra: 01a4c942948ae768e8d995f4a0540be2c08a9e25457a03c9cb07b4e71e12853d0602110000000538edce2e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a45cad4e7a700a97e7539914db277cfc3162d233f53441de1ea78a8591bc9fe 0.600000000000 1667348 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": 1180943, "vin": [ { "gen": { "height": 1180933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a45cad4e7a700a97e7539914db277cfc3162d233f53441de1ea78a8591bc9fe" } } ], "extra": [ 1, 164, 201, 66, 148, 138, 231, 104, 232, 217, 149, 244, 160, 84, 11, 226, 192, 138, 158, 37, 69, 122, 3, 201, 203, 7, 180, 231, 30, 18, 133, 61, 6, 2, 17, 0, 0, 0, 5, 56, 237, 206, 46, 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