Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa211ce6bf278e818550692501b38d59579473f1e0952a80343214b79d4c5e19

Tx prefix hash: 13ce6ca87a1d056ac05690976f5c2b806326052741e2227c0bbd068f38a66fe7
Tx public key: 456a3714a6a92bfe7a36ed6c9fb8f1e91eddcb46715ec60ae49efc171a85cbf7
Timestamp: 1743321426 Timestamp [UCT]: 2025-03-30 07:57:06 Age [y:d:h:m:s]: 00:236:07:06:20
Block: 1250408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166612 RingCT/type: yes/0
Extra: 01456a3714a6a92bfe7a36ed6c9fb8f1e91eddcb46715ec60ae49efc171a85cbf70211000000089ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e278165c263a7d42a20e8bd86f368d80eae151ef1a510bcfc7a1012d75d7cb78 0.600000000000 1737457 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": 1250418, "vin": [ { "gen": { "height": 1250408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e278165c263a7d42a20e8bd86f368d80eae151ef1a510bcfc7a1012d75d7cb78" } } ], "extra": [ 1, 69, 106, 55, 20, 166, 169, 43, 254, 122, 54, 237, 108, 159, 184, 241, 233, 30, 221, 203, 70, 113, 94, 198, 10, 228, 158, 252, 23, 26, 133, 203, 247, 2, 17, 0, 0, 0, 8, 155, 166, 41, 223, 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