Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9fd4d5963b8c1732a19b767897317c6cc58591fc86f8c1a848fc912a5cfba4d

Tx prefix hash: 02fa8a0bfa49d61c8bc7ef12227fbe160b62e371e30c63ed8cfb6ec5c27d5bd9
Tx public key: 2fdc59a78961e1839cb64ec9b3ec8c171e553888c1a3fd5e41f5e8c01b07c83b
Timestamp: 1632338191 Timestamp [UCT]: 2021-09-22 19:16:31 Age [y:d:h:m:s]: 04:039:19:26:21
Block: 339006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1062987 RingCT/type: yes/0
Extra: 012fdc59a78961e1839cb64ec9b3ec8c171e553888c1a3fd5e41f5e8c01b07c83b02110000001a37cb3088000000000000000000

1 output(s) for total of 46.209665791000 dcy

stealth address amount amount idx
00: b1f96918ac3e9706a8cdafc35defeee118adb8b36cd12cbda761f9fd33a322a9 46.209665791000 697423 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": 339016, "vin": [ { "gen": { "height": 339006 } } ], "vout": [ { "amount": 46209665791, "target": { "key": "b1f96918ac3e9706a8cdafc35defeee118adb8b36cd12cbda761f9fd33a322a9" } } ], "extra": [ 1, 47, 220, 89, 167, 137, 97, 225, 131, 156, 182, 78, 201, 179, 236, 140, 23, 30, 85, 56, 136, 193, 163, 253, 94, 65, 245, 232, 192, 27, 7, 200, 59, 2, 17, 0, 0, 0, 26, 55, 203, 48, 136, 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