Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7a0166d9792efc6a93506413e9f8575f71afb68872d01933ea90ef489b223b

Tx prefix hash: 884a6e010dd45441a0ad841765146eca8811ee58da3e1501e1427cafdc122434
Tx public key: f8520aae0c5936ccb4e282ea716eb3c5c3d3318d2c1939436edd10395b8e333f
Timestamp: 1705452241 Timestamp [UCT]: 2024-01-17 00:44:01 Age [y:d:h:m:s]: 01:089:06:29:59
Block: 936919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324912 RingCT/type: yes/0
Extra: 01f8520aae0c5936ccb4e282ea716eb3c5c3d3318d2c1939436edd10395b8e333f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dbfe16bf7f56536117a7c3f22f1cde129659fb0c106cbdef8c7d5efbbf4c142 0.600000000000 1394963 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": 936929, "vin": [ { "gen": { "height": 936919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dbfe16bf7f56536117a7c3f22f1cde129659fb0c106cbdef8c7d5efbbf4c142" } } ], "extra": [ 1, 248, 82, 10, 174, 12, 89, 54, 204, 180, 226, 130, 234, 113, 110, 179, 197, 195, 211, 49, 141, 44, 25, 57, 67, 110, 221, 16, 57, 91, 142, 51, 63, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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