Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ba3eedace1871ff48fec7ad1932e989e3b16a6ffed34e6bc1d3689cef34f91

Tx prefix hash: 74d8ea9dd2599b8c8b9f4a291cfaa33513014869fed7ab3f458634f24a90a6c6
Tx public key: 4ccded2d2c52c0c226822060fdc9aba02c608887f2e75f78098b8a239f2c24ac
Timestamp: 1710842542 Timestamp [UCT]: 2024-03-19 10:02:22 Age [y:d:h:m:s]: 00:311:04:43:34
Block: 981653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222697 RingCT/type: yes/0
Extra: 014ccded2d2c52c0c226822060fdc9aba02c608887f2e75f78098b8a239f2c24ac02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe8c878ffc6f3041343d0e335546f46c415339a1fcb3edb47a9441839935e4f0 0.600000000000 1441750 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": 981663, "vin": [ { "gen": { "height": 981653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe8c878ffc6f3041343d0e335546f46c415339a1fcb3edb47a9441839935e4f0" } } ], "extra": [ 1, 76, 205, 237, 45, 44, 82, 192, 194, 38, 130, 32, 96, 253, 201, 171, 160, 44, 96, 136, 135, 242, 231, 95, 120, 9, 139, 138, 35, 159, 44, 36, 172, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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