Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c78ffad67c6ca620a13fa6e6202adc830600ea5fa7a6074d1d6539148fb6f29

Tx prefix hash: c0e40cf9bce03ce4452e4956c197fb7d6bbc039bfb978bfada09149663317626
Tx public key: d54b9a56b6ce3a7471aa8441b3098edc46cb87349ba029b826e977bd6d4cb231
Timestamp: 1576525609 Timestamp [UCT]: 2019-12-16 19:46:49 Age [y:d:h:m:s]: 05:012:19:05:30
Block: 27927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156437 RingCT/type: yes/0
Extra: 01d54b9a56b6ce3a7471aa8441b3098edc46cb87349ba029b826e977bd6d4cb231021100000007d81c26c0000000000000000000

1 output(s) for total of 495.983377024000 dcy

stealth address amount amount idx
00: 4ffb8557126704d7a3b44c6e0c2a6f2cdd9a59ffc95475d0e47e9e7b9daea7cb 495.983377024000 46205 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": 27937, "vin": [ { "gen": { "height": 27927 } } ], "vout": [ { "amount": 495983377024, "target": { "key": "4ffb8557126704d7a3b44c6e0c2a6f2cdd9a59ffc95475d0e47e9e7b9daea7cb" } } ], "extra": [ 1, 213, 75, 154, 86, 182, 206, 58, 116, 113, 170, 132, 65, 179, 9, 142, 220, 70, 203, 135, 52, 155, 160, 41, 184, 38, 233, 119, 189, 109, 76, 178, 49, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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