Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0782d7ded486fec81cf84cd3a464c2c4c708a2e63f6a0295ab5654b2e256619

Tx prefix hash: b503c8b9554ce6a28ffaeddc2edc24fe6448e362cf83a6fed22b287fca29cd0b
Tx public key: fe1a347c950709c7e68a1e4c22336d8a8f50b9c58639eb1f374f3063355b79a8
Timestamp: 1696584929 Timestamp [UCT]: 2023-10-06 09:35:29 Age [y:d:h:m:s]: 01:220:23:50:19
Block: 863634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419017 RingCT/type: yes/0
Extra: 01fe1a347c950709c7e68a1e4c22336d8a8f50b9c58639eb1f374f3063355b79a8021100000001faf35c9c000000000000000000

1 output(s) for total of 0.844154778000 dcy

stealth address amount amount idx
00: 36876b4ebad86fbcada8006a320f359db3b31a7d58b9c974920aadc80549501d 0.844154778000 1318104 of 0

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": 863644, "vin": [ { "gen": { "height": 863634 } } ], "vout": [ { "amount": 844154778, "target": { "key": "36876b4ebad86fbcada8006a320f359db3b31a7d58b9c974920aadc80549501d" } } ], "extra": [ 1, 254, 26, 52, 124, 149, 7, 9, 199, 230, 138, 30, 76, 34, 51, 109, 138, 143, 80, 185, 197, 134, 57, 235, 31, 55, 79, 48, 99, 53, 91, 121, 168, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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