Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc19483db0f73e60255c106b8073fa4650c2ef5f8d4830fa3e4de1811c48e2fb

Tx prefix hash: 6b5055636ea755ce2f1431c628314cd6cb81e1fc57ce9ca4a9d5e68c3b31414a
Tx public key: 990a37b8b09d109f7b4028f383c314bd5564b764569048223d32650ab015feb5
Timestamp: 1639009126 Timestamp [UCT]: 2021-12-09 00:18:46 Age [y:d:h:m:s]: 03:327:20:15:36
Block: 391406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1010764 RingCT/type: yes/0
Extra: 01990a37b8b09d109f7b4028f383c314bd5564b764569048223d32650ab015feb5021100000002d6e4826b000000000000000000

1 output(s) for total of 30.982025400000 dcy

stealth address amount amount idx
00: d31dc8c3cfa8859648e8aedc1eced8c8307597eff66fa1fc168ef893a3acb0bb 30.982025400000 787795 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": 391416, "vin": [ { "gen": { "height": 391406 } } ], "vout": [ { "amount": 30982025400, "target": { "key": "d31dc8c3cfa8859648e8aedc1eced8c8307597eff66fa1fc168ef893a3acb0bb" } } ], "extra": [ 1, 153, 10, 55, 184, 176, 157, 16, 159, 123, 64, 40, 243, 131, 195, 20, 189, 85, 100, 183, 100, 86, 144, 72, 34, 61, 50, 101, 10, 176, 21, 254, 181, 2, 17, 0, 0, 0, 2, 214, 228, 130, 107, 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