Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7768c1f3c68e4cd94b342724bf645ae5183c8c7af9b3523ff3f030f19356624d

Tx prefix hash: 1547c7bdebb414bf2a3553777fe3574030b16a8cbab704f8ddcb0c7b3a994795
Tx public key: dd49692ca4691b4edcb1d18d479f39b2e86de186dffb4a21368bd9c504b28c72
Timestamp: 1728579347 Timestamp [UCT]: 2024-10-10 16:55:47 Age [y:d:h:m:s]: 00:168:15:49:13
Block: 1128680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120322 RingCT/type: yes/0
Extra: 01dd49692ca4691b4edcb1d18d479f39b2e86de186dffb4a21368bd9c504b28c7202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85d9d3aed0fcfc17e51d28e3ab2ab471b49aa7a49f31662ed310e3fa81d84438 0.600000000000 1611499 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": 1128690, "vin": [ { "gen": { "height": 1128680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85d9d3aed0fcfc17e51d28e3ab2ab471b49aa7a49f31662ed310e3fa81d84438" } } ], "extra": [ 1, 221, 73, 105, 44, 164, 105, 27, 78, 220, 177, 209, 141, 71, 159, 57, 178, 232, 109, 225, 134, 223, 251, 74, 33, 54, 139, 217, 197, 4, 178, 140, 114, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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