Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7426ccb5d1649df2a5483c0960ff5179de08be47101ea88079c700b2371ac0a0

Tx prefix hash: 772c5418fc32414c73d7a31efd7535ef010ba40997885f28601f7157d52d2f8a
Tx public key: 36da46da639b5efe658c5f504d833eda2e01cdfb67b700968a2c18313b3071aa
Timestamp: 1712895469 Timestamp [UCT]: 2024-04-12 04:17:49 Age [y:d:h:m:s]: 00:363:18:31:09
Block: 998632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260086 RingCT/type: yes/0
Extra: 0136da46da639b5efe658c5f504d833eda2e01cdfb67b700968a2c18313b3071aa02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb5f07a246f89d41ba1f92d870aee3e8531dc75a8fd9f7ac77c941cc8ea25d1 0.600000000000 1459084 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": 998642, "vin": [ { "gen": { "height": 998632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb5f07a246f89d41ba1f92d870aee3e8531dc75a8fd9f7ac77c941cc8ea25d1" } } ], "extra": [ 1, 54, 218, 70, 218, 99, 155, 94, 254, 101, 140, 95, 80, 77, 131, 62, 218, 46, 1, 205, 251, 103, 183, 0, 150, 138, 44, 24, 49, 59, 48, 113, 170, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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