Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0fd82e87ac7cd76e4e70a4146b74de9af3e96c58dc2ed760f97e628be9a4a2

Tx prefix hash: 3b836c3b9b38187916850e120b7228b06947ad6aedbb42608d461265203e8f18
Tx public key: 0d4177b0faee23a4214cd772010b1d9dedf20ed33f49c6a07cad515038fbbc2a
Timestamp: 1736107312 Timestamp [UCT]: 2025-01-05 20:01:52 Age [y:d:h:m:s]: 00:107:20:19:44
Block: 1190961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76862 RingCT/type: yes/0
Extra: 010d4177b0faee23a4214cd772010b1d9dedf20ed33f49c6a07cad515038fbbc2a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e24c3a5d7fe54caf79bb64dbc0d4add3a57adadef7b5a4e36e91e414b913f42 0.600000000000 1677484 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": 1190971, "vin": [ { "gen": { "height": 1190961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e24c3a5d7fe54caf79bb64dbc0d4add3a57adadef7b5a4e36e91e414b913f42" } } ], "extra": [ 1, 13, 65, 119, 176, 250, 238, 35, 164, 33, 76, 215, 114, 1, 11, 29, 157, 237, 242, 14, 211, 63, 73, 198, 160, 124, 173, 81, 80, 56, 251, 188, 42, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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