Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3683d02994934a4e700ee79364f12d947f761e0583806e55cea7edf6af095b74

Tx prefix hash: f579381e64e84d8251b6aff062c9fd997a0cb8e40e4e1ee4b716f7e47811bfd3
Tx public key: 998a69d6cc842168be27ff5b58e5445b5b693e8103d7b37724ca9681a839b67a
Timestamp: 1674523284 Timestamp [UCT]: 2023-01-24 01:21:24 Age [y:d:h:m:s]: 02:110:05:20:47
Block: 681403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600443 RingCT/type: yes/0
Extra: 01998a69d6cc842168be27ff5b58e5445b5b693e8103d7b37724ca9681a839b67a0211000000015029cbac000000000000000000

1 output(s) for total of 3.390228244000 dcy

stealth address amount amount idx
00: e64a9d1f897777cae3bd8c1d65d79b41190612aaf68098fb09d2a75b396005c4 3.390228244000 1123492 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": 681413, "vin": [ { "gen": { "height": 681403 } } ], "vout": [ { "amount": 3390228244, "target": { "key": "e64a9d1f897777cae3bd8c1d65d79b41190612aaf68098fb09d2a75b396005c4" } } ], "extra": [ 1, 153, 138, 105, 214, 204, 132, 33, 104, 190, 39, 255, 91, 88, 229, 68, 91, 91, 105, 62, 129, 3, 215, 179, 119, 36, 202, 150, 129, 168, 57, 182, 122, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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