Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f4a6349fd49f929e4fa7f9cd9bfe4e95f2355e60c4d668a5221029ab74fbb7

Tx prefix hash: aeacfffc1abf0c5258201e7ef5fbb549e03db8d711ee9fe65f0aec3742eb8ccb
Tx public key: f0a2671272fc44d2b59c3ecfb686a22fe5bec439872559477d3f4f14a1e4c802
Timestamp: 1734583330 Timestamp [UCT]: 2024-12-19 04:42:10 Age [y:d:h:m:s]: 00:112:00:39:55
Block: 1178368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79837 RingCT/type: yes/0
Extra: 01f0a2671272fc44d2b59c3ecfb686a22fe5bec439872559477d3f4f14a1e4c80202110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3762fa57713fb272f70c70fb0b869e27a780951141a98374966f60c16650226e 0.600000000000 1664755 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": 1178378, "vin": [ { "gen": { "height": 1178368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3762fa57713fb272f70c70fb0b869e27a780951141a98374966f60c16650226e" } } ], "extra": [ 1, 240, 162, 103, 18, 114, 252, 68, 210, 181, 156, 62, 207, 182, 134, 162, 47, 229, 190, 196, 57, 135, 37, 89, 71, 125, 63, 79, 20, 161, 228, 200, 2, 2, 17, 0, 0, 0, 12, 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