Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13698beb708124fd65ba13b5cdc6f88bd57879eeb763bfd21384dfbb0e4ddd2

Tx prefix hash: 614ef9b7ff7216dcb4e92148b4dcce84076398aae25cc1c860f896b11faee6ed
Tx public key: e4b56d68a86ba6f9fa0d998ef82c4c231377b20ae8b65f67d2fec63de63327ff
Timestamp: 1713128770 Timestamp [UCT]: 2024-04-14 21:06:10 Age [y:d:h:m:s]: 01:054:02:45:50
Block: 1000574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299675 RingCT/type: yes/0
Extra: 01e4b56d68a86ba6f9fa0d998ef82c4c231377b20ae8b65f67d2fec63de63327ff02110000001759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02eee4a51e4cc4e766529bf82a98b08f29fef6a8461c047e03624d096c5774c6 0.600000000000 1461072 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": 1000584, "vin": [ { "gen": { "height": 1000574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02eee4a51e4cc4e766529bf82a98b08f29fef6a8461c047e03624d096c5774c6" } } ], "extra": [ 1, 228, 181, 109, 104, 168, 107, 166, 249, 250, 13, 153, 142, 248, 44, 76, 35, 19, 119, 178, 10, 232, 182, 95, 103, 210, 254, 198, 61, 230, 51, 39, 255, 2, 17, 0, 0, 0, 23, 89, 218, 211, 245, 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