Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7443b382189e07a959551f09425b139ff493fa96b837e175de5f583228bd4f1

Tx prefix hash: 316b6272e9cbf02a699c2e5550d20519ffde55079e4af4b3b5fd5074ade147b6
Tx public key: 21b1b5af0668e63e4c07e33cae9df4b25b2966a78c692df9b20be0944ca1ff27
Timestamp: 1580700158 Timestamp [UCT]: 2020-02-03 03:22:38 Age [y:d:h:m:s]: 04:347:23:49:42
Block: 57588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140017 RingCT/type: yes/0
Extra: 0121b1b5af0668e63e4c07e33cae9df4b25b2966a78c692df9b20be0944ca1ff27021100000004bd0f9f9f000000000000000000

1 output(s) for total of 395.552799167000 dcy

stealth address amount amount idx
00: 4a3a97be3a79a7fc45a596128fdbd9601e631c0399e157e6bf3ab7a14ea663d5 395.552799167000 106447 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": 57598, "vin": [ { "gen": { "height": 57588 } } ], "vout": [ { "amount": 395552799167, "target": { "key": "4a3a97be3a79a7fc45a596128fdbd9601e631c0399e157e6bf3ab7a14ea663d5" } } ], "extra": [ 1, 33, 177, 181, 175, 6, 104, 230, 62, 76, 7, 227, 60, 174, 157, 244, 178, 91, 41, 102, 167, 140, 105, 45, 249, 178, 11, 224, 148, 76, 161, 255, 39, 2, 17, 0, 0, 0, 4, 189, 15, 159, 159, 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