Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a569d62937ad9df6aea149ac48a057816115093540c4fc21595d8a0ded1c4f5

Tx prefix hash: a6d9cc15494db226276a2dbb69548e3e1325d6b383bb533077b36f9ac974af1e
Tx public key: 4244f9577a9d0debbad6e28fa03ecf13e5751341da4fb9d8b72a084208c3bd43
Timestamp: 1758876501 Timestamp [UCT]: 2025-09-26 08:48:21 Age [y:d:h:m:s]: 00:045:12:46:01
Block: 1376754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32597 RingCT/type: yes/0
Extra: 014244f9577a9d0debbad6e28fa03ecf13e5751341da4fb9d8b72a084208c3bd43021100000009ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6938eeafd6659095d5a10b76d79960d211497d0a583c561dfbb3e54cba6ae1f7 0.600000000000 1864845 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": 1376764, "vin": [ { "gen": { "height": 1376754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6938eeafd6659095d5a10b76d79960d211497d0a583c561dfbb3e54cba6ae1f7" } } ], "extra": [ 1, 66, 68, 249, 87, 122, 157, 13, 235, 186, 214, 226, 143, 160, 62, 207, 19, 229, 117, 19, 65, 218, 79, 185, 216, 183, 42, 8, 66, 8, 195, 189, 67, 2, 17, 0, 0, 0, 9, 173, 121, 72, 208, 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