Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4149cf73681cbdbaf9299fa8b6b2e145a123ee4d8e470d4ca616794206fa1279

Tx prefix hash: 17febe400cabfa561b330c4e6794b45fc0aee91edc9cbf2b02922024c7ab7e77
Tx public key: 7f5b2b3040676e7ad6f9e792e45743f66249a4be8a663b8b6da226b3fa7d66df
Timestamp: 1752883811 Timestamp [UCT]: 2025-07-19 00:10:11 Age [y:d:h:m:s]: 00:168:08:09:16
Block: 1328462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119162 RingCT/type: yes/0
Extra: 017f5b2b3040676e7ad6f9e792e45743f66249a4be8a663b8b6da226b3fa7d66df02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 691234a2bd434fcce53754b8611b8a9606eb088d1dbc6936c498eecaa9ce5aac 0.600000000000 1816225 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": 1328472, "vin": [ { "gen": { "height": 1328462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "691234a2bd434fcce53754b8611b8a9606eb088d1dbc6936c498eecaa9ce5aac" } } ], "extra": [ 1, 127, 91, 43, 48, 64, 103, 110, 122, 214, 249, 231, 146, 228, 87, 67, 246, 98, 73, 164, 190, 138, 102, 59, 139, 109, 162, 38, 179, 250, 125, 102, 223, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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