Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdabb70c66910634f62f9f31b1d0fc97c3f05c09954037b7115093572c30a07e

Tx prefix hash: 6df34981c413ebe391432f4d9c775224416c0c79acdde665ec82f526501e8e46
Tx public key: 298cac45fdb4d40b391d487b327ed341b9839f56e59d1c8be0c87ec5887bf6a4
Timestamp: 1726994207 Timestamp [UCT]: 2024-09-22 08:36:47 Age [y:d:h:m:s]: 00:107:12:11:36
Block: 1115543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76869 RingCT/type: yes/0
Extra: 01298cac45fdb4d40b391d487b327ed341b9839f56e59d1c8be0c87ec5887bf6a4021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 623ffa6badea8f50bb2e1c961c9769f76f6f52968edbaab8fd8c6300e973912d 0.600000000000 1595712 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": 1115553, "vin": [ { "gen": { "height": 1115543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "623ffa6badea8f50bb2e1c961c9769f76f6f52968edbaab8fd8c6300e973912d" } } ], "extra": [ 1, 41, 140, 172, 69, 253, 180, 212, 11, 57, 29, 72, 123, 50, 126, 211, 65, 185, 131, 159, 86, 229, 157, 28, 139, 224, 200, 126, 197, 136, 123, 246, 164, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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