Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6b46e1cd92abc581dfc541a66bd9687e27ceb77bc3eb927d0938480ac6a40a

Tx prefix hash: e676263f62b94eee05e82b30cb4d15a76237bf2d5b3dd579ed2a4e85c9b35cb5
Tx public key: d833c210a9c4a480f47a1cb70cb88a5f1cebe590e0ff229de8fb10d6e82b404f
Timestamp: 1753828398 Timestamp [UCT]: 2025-07-29 22:33:18 Age [y:d:h:m:s]: 00:020:21:32:28
Block: 1336227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13860 RingCT/type: yes/0
Extra: 01d833c210a9c4a480f47a1cb70cb88a5f1cebe590e0ff229de8fb10d6e82b404f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9de5287e2058b0d568ef1552ae2ff97a23d9c496cecd3a94e6f5912fcd58cb01 0.600000000000 1824028 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": 1336237, "vin": [ { "gen": { "height": 1336227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9de5287e2058b0d568ef1552ae2ff97a23d9c496cecd3a94e6f5912fcd58cb01" } } ], "extra": [ 1, 216, 51, 194, 16, 169, 196, 164, 128, 244, 122, 28, 183, 12, 184, 138, 95, 28, 235, 229, 144, 224, 255, 34, 157, 232, 251, 16, 214, 232, 43, 64, 79, 2, 17, 0, 0, 0, 1, 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