Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c6df3b6743ad4b8a13fd0da61dcc221656d1df498ee513d717e40ea38beb4a

Tx prefix hash: aff9f45e5c7ae4716d1ed7b4f2c3b73b98cb90b786191f83e8bb8f37108aa9ca
Tx public key: c78387427830a5fab73109dc887ec72ecf9f0ebaf59b861015ec1eeebecfd475
Timestamp: 1734507540 Timestamp [UCT]: 2024-12-18 07:39:00 Age [y:d:h:m:s]: 00:107:00:14:23
Block: 1177745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76241 RingCT/type: yes/0
Extra: 01c78387427830a5fab73109dc887ec72ecf9f0ebaf59b861015ec1eeebecfd47502110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65f7cd1c1d7fd5b553261600295cf8625bb9ebcd4406aaa777529c675a7eb600 0.600000000000 1664122 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": 1177755, "vin": [ { "gen": { "height": 1177745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65f7cd1c1d7fd5b553261600295cf8625bb9ebcd4406aaa777529c675a7eb600" } } ], "extra": [ 1, 199, 131, 135, 66, 120, 48, 165, 250, 183, 49, 9, 220, 136, 126, 199, 46, 207, 159, 14, 186, 245, 155, 134, 16, 21, 236, 30, 238, 190, 207, 212, 117, 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