Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc84a2eab24a607918b0dc6c131146384516e0757976774d4f9cc07f5a028c05

Tx prefix hash: 17fe74cdb8d75977d0b2f9565cc938bb136ef1b494b75d2e78665e98b23ee60b
Tx public key: b90ce75d99cebdc208b72310eead029627f9b588c2879c99f4f72dcfbef2ba4a
Timestamp: 1631739300 Timestamp [UCT]: 2021-09-15 20:55:00 Age [y:d:h:m:s]: 04:047:00:20:37
Block: 334519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067670 RingCT/type: yes/0
Extra: 01b90ce75d99cebdc208b72310eead029627f9b588c2879c99f4f72dcfbef2ba4a02110000000ba272b9cb000000000000000000

1 output(s) for total of 47.819790103000 dcy

stealth address amount amount idx
00: e6138bd7d5ef99e08a8f169bcd8606d5e53d1fd8ab6124761d57d165d6a9abd1 47.819790103000 689950 of 0

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": 334529, "vin": [ { "gen": { "height": 334519 } } ], "vout": [ { "amount": 47819790103, "target": { "key": "e6138bd7d5ef99e08a8f169bcd8606d5e53d1fd8ab6124761d57d165d6a9abd1" } } ], "extra": [ 1, 185, 12, 231, 93, 153, 206, 189, 194, 8, 183, 35, 16, 238, 173, 2, 150, 39, 249, 181, 136, 194, 135, 156, 153, 244, 247, 45, 207, 190, 242, 186, 74, 2, 17, 0, 0, 0, 11, 162, 114, 185, 203, 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