Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c61aac095a5aebc67eb183e687d3a37990eefc06634cd48c5c0b893dd600ec4

Tx prefix hash: 551377755c0981e86f0e213afb958b52a55b4620a04c89741a3ff2cde2dc0fbf
Tx public key: abd605a850aa6f182156de84d9159cc25b278b9bcab6aacca41a9d3ac45f49bc
Timestamp: 1707873946 Timestamp [UCT]: 2024-02-14 01:25:46 Age [y:d:h:m:s]: 01:046:00:08:26
Block: 957022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293907 RingCT/type: yes/0
Extra: 01abd605a850aa6f182156de84d9159cc25b278b9bcab6aacca41a9d3ac45f49bc02110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36bac5f3acfc5d38f9a7ea92d96686c5e8d578bea59f4502de7f49ccf797956 0.600000000000 1416336 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": 957032, "vin": [ { "gen": { "height": 957022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36bac5f3acfc5d38f9a7ea92d96686c5e8d578bea59f4502de7f49ccf797956" } } ], "extra": [ 1, 171, 214, 5, 168, 80, 170, 111, 24, 33, 86, 222, 132, 217, 21, 156, 194, 91, 39, 139, 155, 202, 182, 170, 204, 164, 26, 157, 58, 196, 95, 73, 188, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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