Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1779073bf08e5f607be6ac74b7b1edacf1ac25b40ab7afa1219bffa70258804c

Tx prefix hash: f17f61c2b0af3e9ee5f804272a2427e4fc0e807c3d765a384c85eb5ed7c4be6b
Tx public key: a312d0f41a3468e6824cc2bb3812269d8c8fa1ef816be59c18ae4f55c30b5e09
Timestamp: 1750609204 Timestamp [UCT]: 2025-06-22 16:20:04 Age [y:d:h:m:s]: 00:139:17:13:24
Block: 1310551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97723 RingCT/type: yes/0
Extra: 01a312d0f41a3468e6824cc2bb3812269d8c8fa1ef816be59c18ae4f55c30b5e090211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 411d4e0ebe45dbf9ddce6642cd51ab366bdde0c7465e5e33a6ef4adce0df7899 0.600000000000 1798172 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": 1310561, "vin": [ { "gen": { "height": 1310551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "411d4e0ebe45dbf9ddce6642cd51ab366bdde0c7465e5e33a6ef4adce0df7899" } } ], "extra": [ 1, 163, 18, 208, 244, 26, 52, 104, 230, 130, 76, 194, 187, 56, 18, 38, 157, 140, 143, 161, 239, 129, 107, 229, 156, 24, 174, 79, 85, 195, 11, 94, 9, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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