Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50f776863c1745b708de99ef49e4be2d3a02f8f8fc49d19e5fe886a90646419

Tx prefix hash: 49d6f1a7dcb23f3298dfd5e95fb7129fd077291517b1942969e0abb26e44de4b
Tx public key: cfd3c121f4703539b0c9455a2ea238a119b516dc59fa8b917105997cd643ce87
Timestamp: 1731977435 Timestamp [UCT]: 2024-11-19 00:50:35 Age [y:d:h:m:s]: 00:137:13:37:25
Block: 1156765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98131 RingCT/type: yes/0
Extra: 01cfd3c121f4703539b0c9455a2ea238a119b516dc59fa8b917105997cd643ce87021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 667c9088b2a70349cd33b4d3b566476329e71d9de0a67de63a5287dd972b1d6c 0.600000000000 1642388 of 15

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": 1156775, "vin": [ { "gen": { "height": 1156765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "667c9088b2a70349cd33b4d3b566476329e71d9de0a67de63a5287dd972b1d6c" } } ], "extra": [ 1, 207, 211, 193, 33, 244, 112, 53, 57, 176, 201, 69, 90, 46, 162, 56, 161, 25, 181, 22, 220, 89, 250, 139, 145, 113, 5, 153, 124, 214, 67, 206, 135, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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