Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b4b172f6ab7e6410f2e63459b64490f7352a97ad11eb95f3231248d24e15df8

Tx prefix hash: 0328a7dfae7a7375562170cc5d475e9428391f5296d581fe5b0242c99e935eec
Tx public key: 8d6c1f0a9d6fd8818921ecd9fa640704bc862ecccf8def858a6c5e07069440f6
Timestamp: 1744838625 Timestamp [UCT]: 2025-04-16 21:23:45 Age [y:d:h:m:s]: 00:218:06:39:51
Block: 1262976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153715 RingCT/type: yes/0
Extra: 018d6c1f0a9d6fd8818921ecd9fa640704bc862ecccf8def858a6c5e07069440f602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f9f151fa8e84419b750cf7bef0c1796d7039c78eef345949f1227a6a050499 0.600000000000 1750159 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": 1262986, "vin": [ { "gen": { "height": 1262976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f9f151fa8e84419b750cf7bef0c1796d7039c78eef345949f1227a6a050499" } } ], "extra": [ 1, 141, 108, 31, 10, 157, 111, 216, 129, 137, 33, 236, 217, 250, 100, 7, 4, 188, 134, 46, 204, 207, 141, 239, 133, 138, 108, 94, 7, 6, 148, 64, 246, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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