Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6facff0f83c4daab151bc0fd4ad142e1d5895017afe19a9c35aae6f5cfd5670b

Tx prefix hash: cb52c7816e89db21d7e5dca82dbfaed1f2521da318f9cab7add99a3ec3558f62
Tx public key: ea3ee2afe8271c1d454906f5320c27ed41f1ba0fe12a7d097429fd729ffccd06
Timestamp: 1756067731 Timestamp [UCT]: 2025-08-24 20:35:31 Age [y:d:h:m:s]: 00:093:18:36:49
Block: 1353659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66958 RingCT/type: yes/0
Extra: 01ea3ee2afe8271c1d454906f5320c27ed41f1ba0fe12a7d097429fd729ffccd060211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 244856ebfab94d037fa7ee5c1869f4709ccecb2f71093574eef3610deff6b76c 0.600000000000 1841636 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": 1353669, "vin": [ { "gen": { "height": 1353659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "244856ebfab94d037fa7ee5c1869f4709ccecb2f71093574eef3610deff6b76c" } } ], "extra": [ 1, 234, 62, 226, 175, 232, 39, 28, 29, 69, 73, 6, 245, 50, 12, 39, 237, 65, 241, 186, 15, 225, 42, 125, 9, 116, 41, 253, 114, 159, 252, 205, 6, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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