Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6def161ae1ce8bbf96af76105795b6f42f3ba2f6910ea4d3870e85857df62a0

Tx prefix hash: a0a3bd3706f53b7834d40447ef5054544ffa265479fe12c8d945fc8015c9c5a7
Tx public key: 8a81fcd5c2e5cf237819f2194f6168b0cc24f47f2e1791618952f5cdbb16d209
Timestamp: 1697960764 Timestamp [UCT]: 2023-10-22 07:46:04 Age [y:d:h:m:s]: 01:089:11:33:27
Block: 875044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325161 RingCT/type: yes/0
Extra: 018a81fcd5c2e5cf237819f2194f6168b0cc24f47f2e1791618952f5cdbb16d20902110000000433af99f4000000000000000000

1 output(s) for total of 0.773807327000 dcy

stealth address amount amount idx
00: a2d9435987661ce2cbc62f54f3576b0ee0c1ea91d398ff923b6ec18118ffa8b9 0.773807327000 1330284 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": 875054, "vin": [ { "gen": { "height": 875044 } } ], "vout": [ { "amount": 773807327, "target": { "key": "a2d9435987661ce2cbc62f54f3576b0ee0c1ea91d398ff923b6ec18118ffa8b9" } } ], "extra": [ 1, 138, 129, 252, 213, 194, 229, 207, 35, 120, 25, 242, 25, 79, 97, 104, 176, 204, 36, 244, 127, 46, 23, 145, 97, 137, 82, 245, 205, 187, 22, 210, 9, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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