Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0419c07d463cdc6e5c99e57f3a0913dcc4acc312b7c400b1ca1012f20b916e1

Tx prefix hash: 0d706f8f9ad2376fe7623eb21cdf9c2041b0c0d292dff449d250ed2203080a88
Tx public key: 3ce22f55cb6e28115d3aff445f7204e83e35bde02627d59a92a2c6d4165db9ee
Timestamp: 1583931938 Timestamp [UCT]: 2020-03-11 13:05:38 Age [y:d:h:m:s]: 04:240:02:19:46
Block: 80448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1066726 RingCT/type: yes/0
Extra: 013ce22f55cb6e28115d3aff445f7204e83e35bde02627d59a92a2c6d4165db9ee02110000002078e4872e000000000000000000

1 output(s) for total of 332.233307473000 dcy

stealth address amount amount idx
00: 89765d7aa3ebb3c05fab093a15cf937f0d809e3ac9b480056f84e299634efd6e 332.233307473000 147236 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": 80458, "vin": [ { "gen": { "height": 80448 } } ], "vout": [ { "amount": 332233307473, "target": { "key": "89765d7aa3ebb3c05fab093a15cf937f0d809e3ac9b480056f84e299634efd6e" } } ], "extra": [ 1, 60, 226, 47, 85, 203, 110, 40, 17, 93, 58, 255, 68, 95, 114, 4, 232, 62, 53, 189, 224, 38, 39, 213, 154, 146, 162, 198, 212, 22, 93, 185, 238, 2, 17, 0, 0, 0, 32, 120, 228, 135, 46, 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