Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426b7cb397a0bc957a0d66e163d840372cd4f74561e3b92127fa2828ddf7dd11

Tx prefix hash: b99e8368c6ca70f8d45bef1e6118a458a086ed8000e83a6309d58997bc9ce2f3
Tx public key: 5aa3499147078be934f7dce939451ceadffbadbc4fd51cbfe588e95ec6e3c34c
Timestamp: 1750620247 Timestamp [UCT]: 2025-06-22 19:24:07 Age [y:d:h:m:s]: 00:144:13:26:23
Block: 1310629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101211 RingCT/type: yes/0
Extra: 015aa3499147078be934f7dce939451ceadffbadbc4fd51cbfe588e95ec6e3c34c02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebf0ecb22afec81c626e3a41490a32d1c6b6c954a623e228464e003f0fd3f506 0.600000000000 1798250 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": 1310639, "vin": [ { "gen": { "height": 1310629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebf0ecb22afec81c626e3a41490a32d1c6b6c954a623e228464e003f0fd3f506" } } ], "extra": [ 1, 90, 163, 73, 145, 71, 7, 139, 233, 52, 247, 220, 233, 57, 69, 28, 234, 223, 251, 173, 188, 79, 213, 28, 191, 229, 136, 233, 94, 198, 227, 195, 76, 2, 17, 0, 0, 0, 3, 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