Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4f2641b92aa4c0e7b1bb2c806754d1d707bd685dc93c860195598a8196401b

Tx prefix hash: 5bf0c053b1c079c57ffdc07b5157c2cf80bb99e8c26292550c061d7958534012
Tx public key: 8ebe43f40d0c0c7531d36437a290692c4afdfd6cda110825e6f373ede41419d6
Timestamp: 1732315633 Timestamp [UCT]: 2024-11-22 22:47:13 Age [y:d:h:m:s]: 00:136:13:23:53
Block: 1159568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97397 RingCT/type: yes/0
Extra: 018ebe43f40d0c0c7531d36437a290692c4afdfd6cda110825e6f373ede41419d6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fdc06e6d39a39411106b05cce7efe294b6dfb5dad396e6906aecafaffc65bc8 0.600000000000 1645207 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": 1159578, "vin": [ { "gen": { "height": 1159568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fdc06e6d39a39411106b05cce7efe294b6dfb5dad396e6906aecafaffc65bc8" } } ], "extra": [ 1, 142, 190, 67, 244, 13, 12, 12, 117, 49, 211, 100, 55, 162, 144, 105, 44, 74, 253, 253, 108, 218, 17, 8, 37, 230, 243, 115, 237, 228, 20, 25, 214, 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