Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 593b22ea36d757c7a7766ad97317e7289082475341a7d7c5d9e13a89105436b9

Tx prefix hash: 5ad46a52e85f820c5b547cf7343d2394dd4edc039657d512919ef4a7dce13765
Tx public key: 393aecf0932f7edbc3740bbb9ec0d39d7b3488a12be3a6ed455b0114bb220a30
Timestamp: 1722566457 Timestamp [UCT]: 2024-08-02 02:40:57 Age [y:d:h:m:s]: 00:252:09:28:08
Block: 1078830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180301 RingCT/type: yes/0
Extra: 01393aecf0932f7edbc3740bbb9ec0d39d7b3488a12be3a6ed455b0114bb220a3002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0abb70b29b5b4260b2ea9d3ca42c2e0a1477c760c6ee6be452c6b3adaf3a0275 0.600000000000 1551527 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": 1078840, "vin": [ { "gen": { "height": 1078830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0abb70b29b5b4260b2ea9d3ca42c2e0a1477c760c6ee6be452c6b3adaf3a0275" } } ], "extra": [ 1, 57, 58, 236, 240, 147, 47, 126, 219, 195, 116, 11, 187, 158, 192, 211, 157, 123, 52, 136, 161, 43, 227, 166, 237, 69, 91, 1, 20, 187, 34, 10, 48, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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