Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98a1a57c6653ee01d84d4cc3d728848dfdb331af8aa173502525b35e710430e3

Tx prefix hash: 41a97de420bca6363337030fb61ecf40c2b02d26efe6a97ef99b956b5b637689
Tx public key: ea40a4aaa4ef48d2c376fd32470bffc857086892cc52b86cc03c49bed7bcd24d
Timestamp: 1581948663 Timestamp [UCT]: 2020-02-17 14:11:03 Age [y:d:h:m:s]: 04:286:22:35:19
Block: 66810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097472 RingCT/type: yes/0
Extra: 01ea40a4aaa4ef48d2c376fd32470bffc857086892cc52b86cc03c49bed7bcd24d02110000000256c366d3000000000000000000

1 output(s) for total of 368.664690425000 dcy

stealth address amount amount idx
00: 3705e66e8eefd491b61076cf5e5bef5d1f509799cba7cf95b741e43d09f4f4ff 368.664690425000 123016 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": 66820, "vin": [ { "gen": { "height": 66810 } } ], "vout": [ { "amount": 368664690425, "target": { "key": "3705e66e8eefd491b61076cf5e5bef5d1f509799cba7cf95b741e43d09f4f4ff" } } ], "extra": [ 1, 234, 64, 164, 170, 164, 239, 72, 210, 195, 118, 253, 50, 71, 11, 255, 200, 87, 8, 104, 146, 204, 82, 184, 108, 192, 60, 73, 190, 215, 188, 210, 77, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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