Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b875759f30b1f5f2eb522aceb3664dae6c8fe8d1c205e6335d93bf9910ac4713

Tx prefix hash: 04d5eb35d920dc37b5b2d9100366bd413fec364a8aff211545d90bae51dee9de
Tx public key: 8a2dd99ad77c4117df8defdd9df07ebd0f29b1812f7ce20ce6dcc2a1347c31b4
Timestamp: 1733068926 Timestamp [UCT]: 2024-12-01 16:02:06 Age [y:d:h:m:s]: 00:113:03:49:49
Block: 1165807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80662 RingCT/type: yes/0
Extra: 018a2dd99ad77c4117df8defdd9df07ebd0f29b1812f7ce20ce6dcc2a1347c31b4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a206c2856903b8bde209499a91967af8da4e62e21979096567564a894e992dff 0.600000000000 1651482 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": 1165817, "vin": [ { "gen": { "height": 1165807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a206c2856903b8bde209499a91967af8da4e62e21979096567564a894e992dff" } } ], "extra": [ 1, 138, 45, 217, 154, 215, 124, 65, 23, 223, 141, 239, 221, 157, 240, 126, 189, 15, 41, 177, 129, 47, 124, 226, 12, 230, 220, 194, 161, 52, 124, 49, 180, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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