Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f915427bfb58931d8a57cb4f3625fa6b04881f19c5039bc6c5191670bef3586

Tx prefix hash: 894382c945de00a6d858d180348b799f21f7d04e8ef235b3d980ae6f76b40b2b
Tx public key: 6b2cd07af7f6c8165141cf1a8b2955d12332aedc2a314172efd55578ae94ffb8
Timestamp: 1707084500 Timestamp [UCT]: 2024-02-04 22:08:20 Age [y:d:h:m:s]: 01:116:07:18:38
Block: 950469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344229 RingCT/type: yes/0
Extra: 016b2cd07af7f6c8165141cf1a8b2955d12332aedc2a314172efd55578ae94ffb802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fded7285b5d64260adc9a37c60077aa6e68bd9c9fe016da6c53b8fd87973a60c 0.600000000000 1409097 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": 950479, "vin": [ { "gen": { "height": 950469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fded7285b5d64260adc9a37c60077aa6e68bd9c9fe016da6c53b8fd87973a60c" } } ], "extra": [ 1, 107, 44, 208, 122, 247, 246, 200, 22, 81, 65, 207, 26, 139, 41, 85, 209, 35, 50, 174, 220, 42, 49, 65, 114, 239, 213, 85, 120, 174, 148, 255, 184, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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